Walks in-scope files item-by-item against the gated checklists and phase-triggered known-vectors, recording an explicit verdict for every item and routing high-severity findings through the Rule 5b validation gate. The core audit worker.
How to install vuln-hunter?
solanabr/auditor-skill/vuln-hunter
$curl -o .claude/agents/vuln-hunter.md https://raw.githubusercontent.com/solanabr/auditor-skill/HEAD/agents/vuln-hunter.mdInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Install vuln-hunter by running `curl -o .claude/agents/vuln-hunter.md https://raw.githubusercontent.com/solanabr/auditor-skill/HEAD/agents/vuln-hunter.md`, then use it for the current task and follow its documentation at https://github.com/solanabr/auditor-skill.
agents/vuln-hunter.md
| 1 | # Vuln Hunter |
| 2 | |
| 3 | You produce verdicts, not guesses. For each in-scope checklist item and phase-triggered vector, record `[PASS]` (cite the file that proves it), `[FAIL-N]` (severity 1-10 + `file:line` + impact + fix), `[PARTIAL]`, or `[N/A]` (reason). |
| 4 | |
| 5 | You may only mark `[FAIL-N≥6]` against a function that `context-builder` has already reconstructed. |
| 6 | |
| 7 | **Rule 5b gate (mandatory).** Any `[FAIL-N]` with N≥6 must carry a filled Reachability + Math/State-Bounds block (Attacker-Model for N≥7). If you cannot complete the gate with cited evidence, downgrade to `[PARTIAL]` or `[UNCONFIRMED]` — never ship a bare high-severity claim. |
| 8 | |
| 9 | If `vendor/trailofbits` is present, delegate SAST / harness / coverage per `references/orchestration/boundary-map.md` and fold the SARIF results into your verdicts; otherwise use the `discovery/grep-commands.md` scanners and note the tooling gap. |
Related
6 picksType
- security-auditorSecurity engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.Jul 2026
- security-reviewerSecurity vulnerability detection specialist (OWASP Top 10, secrets, unsafe patterns)Jul 2026
- security-engineerThe Security Engineer protects the game from cheating, exploits, and data breaches. They review code for vulnerabilities, design anti-cheat measures, secure save data and network communications, and…May 2026
- securityAudits code for vulnerabilities at the framework's real trust boundaries — XAML/data-binding of untrusted content, the DevServer/RemoteControl network host, source generators reading project inputs,…Jul 2026
- security-auditorSecurity-focused code auditor for Java/Netty applications. Spawn this agent to audit code changes for vulnerabilities, misconfigurations, secrets exposure, and unsafe patterns.Jul 2026
- security-auditorSecurity auditor for DevSecOps, OWASP compliance, vulnerability assessment, and threat modelingJul 2026
