Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Validate security findings for exploitability, reachability, and real-world impact using Bug Hunter-native findings artifacts. Use after security scans, before patch generation, or whenever the user wants confirmation that a suspected vulnerability is actually exploitable.
.claude/skills/codexstar69-vulnerability-validation/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-13 | ✗→✓ | ▲ Improved | 4% | 0% |
| case-16 | ✗→✓ | ▲ Improved | 77% | 0% |
| case-19 | ✗→✓ | ▲ Improved | -14% | 0% |
| case-11 | ✓→✗ | ▼ Worse | -1% | 0% |
| case-04 | ✓→✓ | = Same ✓ | 160% | 0% |
This is a bundled local Bug Hunter companion skill. It strengthens the security-specific parts of the Skeptic/Referee process.
Take suspected or confirmed security findings and answer:
Prefer Bug Hunter-native artifacts:
.bug-hunter/hunter-findings.json.bug-hunter/threat-model.md.bug-hunter/security-config.json.bug-hunter/dep-findings.json when dependency issues are involvedWhen used as a companion to the main pipeline, keep outputs compatible with:
.bug-hunter/referee.json.bug-hunter/report.mdIf a separate validation artifact is helpful for the run, place it under .bug-hunter/validated-findings.json.
.bug-hunter/.Other measured skills in the registry, with their headline benchmark lift.