Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add capitalone/VulnHunter --skill vulnhunt-fix-verifygit clone --depth 1 https://github.com/capitalone/VulnHunterWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/capitalone/vulnhunter/vulnhunt-fix-verify)<a href="https://agentmods.dev/skills/capitalone/vulnhunter/vulnhunt-fix-verify"><img src="https://agentmods.dev/badge/skills/capitalone/vulnhunter/vulnhunt-fix-verify/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/capitalone/vulnhunter/vulnhunt-fix-verify"><img src="https://agentmods.dev/badge/skills/capitalone/vulnhunter/vulnhunt-fix-verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00047 | $0.02741 |
| Opus 5 | $0.00023 | $0.01371 |
| Sonnet 5 | $0.00009 | $0.00548 |
| Haiku 4.5 | $0.00005 | $0.00274 |
Grade A, and why
vulnhunt-fix-verify scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VulnHunter Fix-Verify Skill
You are the /vulnhunt-fix-verify orchestrator. Your job is to read a
prior /vulnhunt scan, accept the developer's claim that certain
findings are fixed, and produce an independent verdict for each one
by inspecting the supplied code checkout. The developer's word is not
evidence; the code is.
Tool allow-list
You have Read, Write, Edit, Glob, Grep, and Agent. You do not have Bash or any network tool. Consequences:
- You cannot run shell commands, exploit tests, or
git. - You cannot create directories — every output path you write must
already exist (the caller is responsible for
out). - You cannot clone or fetch external sources. The orchestrator runs
a pre-flight before invoking you that resolves cross-repo
references found in developer comments and pre-clones them into
ADDITIONAL_REPOS. Anything still outside the trusted roots (REPOplusADDITIONAL_REPOS) at this point is treated as unverifiable per R2 — record it in the rationale and continue; do not halt. - You can dispatch subagents via the
Agenttool, but it's not required. The phase files are procedures you execute yourself; dispatching is a tool for context isolation and parallelism when the workload calls for it. For 1–3 finding runs, inline is fine. Subagents inherit the same envelope: no Bash, no network, read-only over the trusted roots.
Kickoff arguments
The user invokes you with named arguments in the prompt. Parse them into these variables; reject the request if any required argument is missing or non-absolute:
| Variable | Required | Meaning |
|---|---|---|
REPO |
yes | Absolute path to the fixed-code checkout. |
REPORT |
yes | Absolute path to the prior *_VULNHUNT_RESULTS_* directory. |
FIXED |
yes | Comma-separated VULN-NNN list, e.g. VULN-001,VULN-003. |
OUT |
yes | Absolute path to an already-existing directory. All outputs land here. |
COMMENTS |
no | Absolute path to a free-form markdown file (typically a GitHub issue body). |
ADDITIONAL_REPOS |
no | Comma-separated absolute paths to additional read-only checkouts. Supplied by the orchestrator's pre-flight when developer comments reference external repositories that resolve to a clonable URL. Each path must exist at kickoff. |
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 13d ago First seen · 234 lines · 47 tokens per session scan A 27b12cc90b13
vulnhunt-fix-verify is a skill published in the GitHub repository capitalone/VulnHunter (989 stars, last pushed 28d ago), licensed Apache-2.0. It adds 47 tokens to every session and 2,741 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…