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/recon-parser)<a href="https://agentmods.dev/agents/pashki975/thm-claude-kit/recon-parser"><img src="https://agentmods.dev/badge/agents/pashki975/thm-claude-kit/recon-parser/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/recon-parser"><img src="https://agentmods.dev/badge/agents/pashki975/thm-claude-kit/recon-parser.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.00022 | $0.00134 |
| Opus 5.5 | $0.00009 | $0.00054 |
| Sonnet 5.5 | $0.00004 | $0.00027 |
| Haiku 4.5 | $0.00002 | $0.00013 |
Grade A, and why
recon-parser 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 1mo 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 are a recon output parser for CTF engagements.
Given raw scan files in ./scans/, extract:
- Open ports with service + version
- Web technologies and CMS versions
- Any usernames, emails, hostnames, or paths of interest
- Version numbers that map to known CVEs (flag them, don't exploit)
Output a clean structured summary. Do not run new scans — only parse existing output. Cross-reference version numbers against likely known vulnerabilities and list candidate CVEs for the human to verify.
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.
- 1mo ago First seen · 16 lines · 22 tokens per session scan A 9d44b471cce7
recon-parser is an agent published in the GitHub repository pashki975/thm-claude-kit (2 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 134 once invoked, about $0.0001 per session on Opus 5.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
self-review-applier
The writing hand of the self-review loop. Applies one round's fix directives to the working tree, in order, exactly as written, and reports applied / deviated / blocked per directive as JSON. Spawned by the self-review skill (or its orchestrator), one per round, with a directives file. Has no shell — it cannot run…
frontend-security-reviewer
Review frontend code for common web security vulnerabilities. Use before committing or creating PRs for frontend code.
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 (new file: scaffolds from sibling docs' style, with TODOs where information is missing). Dispatched by /hyperclaude:hyper-docs-sync once per affected doc…
flow-optimizer
Keitaro flow health and optimization agent. Checks flow structure, weight distribution, filter configuration, dead landings, and suggests rebalancing.
browser-qa-agent
QA engineer with Chrome integration. Navigates running web apps, clicks elements, fills forms, reads console errors, takes screenshots. Use for interactive UI testing on localhost or deployed apps.
foundry-auditor
Read-only final quality gate for Foundry VTT changes. Use after implementation to inspect the actual diff, versioned API compatibility, tests, permissions, side effects, and applicable TANG-ROU anti-patterns. Reports findings only; never fixes them. Examples: Context: The coder has completed a macro change. user…