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.
git clone --depth 1 https://github.com/pashki975/thm-claude-kitWrote 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/agents/pashki975/thm-claude-kit/cve-researcher)<a href="https://agentmods.dev/agents/pashki975/thm-claude-kit/cve-researcher"><img src="https://agentmods.dev/badge/agents/pashki975/thm-claude-kit/cve-researcher/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/agents/pashki975/thm-claude-kit/cve-researcher"><img src="https://agentmods.dev/badge/agents/pashki975/thm-claude-kit/cve-researcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00017 | $0.00153 |
| Opus 5 | $0.00009 | $0.00077 |
| Sonnet 5 | $0.00003 | $0.00031 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
cve-researcher 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 9d 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.
What it actually says
You research known vulnerabilities for CTF targets.
Given service names and versions (from nmap -sV, whatweb, etc.):
- List candidate CVEs with a one-line description and severity
- Note whether a public PoC / Metasploit module / searchsploit entry likely exists
- Run
searchsploit <product> <version>to check the local exploit-db copy - Rank by exploitability in a CTF context (working public exploit > theoretical)
Verify version numbers before asserting a CVE applies. Flag uncertainty. Do NOT download or run exploit code — hand the human a verified shortlist.
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.
- 9d ago First seen · 16 lines · 17 tokens per session scan A b3e5853f84a8
cve-researcher is an agent published in the GitHub repository pashki975/thm-claude-kit (2 stars, last pushed 26d ago), licensed MIT. It adds 17 tokens to every session and 153 once invoked, about $0.0001 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-31.
Other agents, from other repositories
requirements-doc-agent
Lightweight requirements documentation sub-agent modelled on the doc-coauthoring pattern. Dispatched by the exploration-cycle-orchestrator via Copilot CLI (cheap model, many invocations per session). Each invocation handles one focused capture task: problem framing, business requirements, user stories…
debate-synthesizer
Multi-Agent Debate Judge. Receives two or more competing perspectives, proposals, or analyses and synthesizes them into a single hardened conclusion using dialectical reasoning. Resolves conflicts, names tradeoffs, and produces a final verdict.
pr-reviewer
Staff PR Reviewer. Reviews a code diff for correctness, risk, test coverage, and adherence to project conventions. Produces a structured review with inline findings and a ship/hold recommendation.
security-auditor
Senior Security Auditor. Performs OWASP-aligned vulnerability analysis on source code, classifies findings by severity, and produces a structured audit report. Fills the "Security / Edge-Case Auditor" role in the Graph Planning Phase 1 Fan-Out Trio (see graph-planning-superpowers-policy.md §2.3 and…
problem-framing-agent
Phase A agent. Clarifies the problem, user groups, goals, issues, challenges, opportunities, and scope hypotheses during exploration. Dispatched by exploration-cycle-orchestrator-agent or used standalone for initial session framing when a more interactive framing conversation is preferred over the standard…
documenter
Edits one documentation file in-place to reflect code changes — minimal edits, no prose polish, no scope creep. Operates in UPDATE mode (file exists) or CREATE mode (file is new). Dispatched by /hyperclaude:hyper-docs-sync once per affected doc. Context: hyper-docs-sync identified a doc that needs updating after a…