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.
SkillScore73Maintained
Automatic
◆Security & AppSec pack
Last verified 8/19/2026
What it changes
Passed 16 of 22 test cases with the skill, and 14 of 22 without it.
Without skill64%
With skill73%
Checks it passed that the model alone missed
Categorize the exploitability level as HARD.
Provide a benign proof-of-concept demonstration.
Store output files under the .bug-hunter/ directory structure.
3 fixed13 passed either way5 still failing1 broke
Pass-rate lift
+9 pp
Tokens
+0%
Agent turns
0%
Response time
+11%
Model gemini-3.6-flashMeasured 8/19/2026v216 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
Where should custom assessment artifacts produced during the vulnerability evaluation run be placed relative to the workspace root?
What was checked, without and with the skill
Checked
Without skill
With skill
Store output files under the .bug-hunter/ directory structure.
Missed
Passed
case-19 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md54 linessingle file
Vulnerability Validation
This is a bundled local Bug Hunter companion skill. It strengthens the security-specific parts of the Skeptic/Referee process.
Purpose
Take suspected or confirmed security findings and answer:
Is the vulnerable path reachable?
Can an attacker control the input?
Are there existing mitigations?
How exploitable is it really?
What is the CVSS / PoC / impact level?
Inputs
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 involved
Workflow
Read the findings and isolate the security ones.
Trace reachability:
EXTERNAL
AUTHENTICATED
INTERNAL
UNREACHABLE
Trace exploitability:
EASY
MEDIUM
HARD
NOT_EXPLOITABLE
Check for mitigations already present in code, framework behavior, or deployment assumptions.
For confirmed HIGH/CRITICAL security bugs, generate:
exploitation path
benign proof of concept
CVSS vector + score
Feed the result back into Bug Hunter-native verdicting.