vulnerability-validation
/vulnerability-validation
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.
- Author
- codexstar69 ↗
- Repository
- bug-hunter ↗
- Licence
- MIT
- Last repository change
- 17.08.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 17.08.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Original author description
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.
How it works
- Purpose
- Inputs
- Workflow
- Outputs
- Important constraints
SKILL.md preview
--- name: vulnerability-validation description: 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. --- # 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 1. Read the findings and isolate the security ones. 2. Trace reachability: - EXTERNAL - AUTHENTICATED - INTERNAL - UNREACHABLE 3. Trace exploitability: - EASY - MEDIUM - HARD - NOT_EXPLOITABLE 4. Check for mitigations already present in code, framework behavior, or deployment assumptions. 5. For confirmed HIGH/CRITICAL security bugs, generate: - exploitation path - benign proof of concept - CVSS vector + score 6. Feed the result back into Bug Hunter-native verdicting. ## Outputs When used as a companion to the main pipeline, keep outputs compatible with: - `.bug-hunter/referee.json` - `.bug-hunter/report.md` If a separate validation artifact is helpful for the run, place it under `.bug-hunter/validated-findings.json`. ## Important constraints - This skill validates findings; it does not replace the normal fix pipeline. - Keep outputs portable and self-contained under `.bug-hunter/`. - Prefer explicit reasoning for false positives so the user can trust dismissals.
Versions
The database has no other skills named vulnerability-validation.
Database snapshot: 13.11.2026 · package version ebb2574d33cd (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90vulnerability-management
Finds, prioritizes, and closes out vulnerabilities across code, dependencies, images, and infrastructure without drowning the team in unactionable findings. Use this whenever the user is deciding what to patch first, has a scanner producing hundreds of CVEs, is setting patch… - 100verify
This skill should be used when the user asks to "verify fix", "confirm fix", "check if vulnerability is fixed", "validate remediation", "recheck finding", or "test if patch works". Also triggers when the user has applied a security fix and wants confirmation that the… - 100vulnerability-pattern-matcher
Detects security vulnerabilities by matching code against known vulnerability patterns, insecure coding idioms, and CVE-style patterns. Explains why patterns are risky and under what conditions they are exploitable. Use when analyzing code for security issues, reviewing for… - 90exposure-validation
Safely validate whether a vulnerability is actually exposed and exploitable in your environment — reachability, version confirmation, configuration preconditions, non-destructive checks (nmap NSE safe scripts, nuclei with vetted templates, vendor detection scripts) — without… - 100dependency-vulnerability-checker
Validate dependency vulnerability checker operations. Auto-activating skill for Security Fundamentals. Triggers on: dependency vulnerability checker, dependency vulnerability checker Part of the Security Fundamentals skill category. Use when working with dependency vulnerability… - 90fp-check
Systematically verifies suspected security bugs to eliminate false positives, producing a TRUE POSITIVE or FALSE POSITIVE verdict with documented evidence for each. Use when asked whether a specific finding is real, exploitable, or a false positive, or to verify or validate a…