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 agentmods add commands/pashki975/thm-claude-kit/recongit 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/commands/pashki975/thm-claude-kit/recon)<a href="https://agentmods.dev/commands/pashki975/thm-claude-kit/recon"><img src="https://agentmods.dev/badge/commands/pashki975/thm-claude-kit/recon.svg" alt="Measured on agentmods" 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.00011 | $0.00172 |
| Opus 5 | $0.00005 | $0.00086 |
| Sonnet 5 | $0.00002 | $0.00034 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
recon 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 5d 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
Run reconnaissance against target IP: $ARGUMENTS
Steps:
- Create ./scans/ if it doesn't exist
- Fast port discovery:
nmap -p- --min-rate 5000 -T4 $ARGUMENTS -oN scans/nmap-allports.txt - Parse open ports, then run a targeted service/version + default-script scan on ONLY those ports:
nmap -sV -sC -p<open_ports> $ARGUMENTS -oN scans/nmap-services.txt - Summarize: table of port | service | version | notes
- Update notes.md with the target IP and discovered services
- Propose the next 2-3 enumeration steps based on what's open
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.
- 5d ago First seen · 15 lines · 11 tokens per session scan A 6f9ac022b792
recon is a command published in the GitHub repository pashki975/thm-claude-kit (2 stars, last pushed 22d ago), licensed MIT. It adds 11 tokens to every session and 172 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 commands, from other repositories
send
Send a message to a peer session.
project-status
Summarize the current state of this client project.
pr
Create a pull request from the current branch.
wiki-query
Answer a question from the wiki's accumulated knowledge using index-first retrieval.
wf-statusline
Set up a lightweight, artifact-only workflow progress statusline.
calibrate-voice
Run an empirical calibration round: regenerate the 8-brief matrix, measure, collect owner ratings, codify every reaction into a logged pack change.