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/nnnsightnnn/claudekit/hooks-analyzergit clone --depth 1 https://github.com/Nnnsightnnn/claudekitWrote 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/nnnsightnnn/claudekit/hooks-analyzer)<a href="https://agentmods.dev/commands/nnnsightnnn/claudekit/hooks-analyzer"><img src="https://agentmods.dev/badge/commands/nnnsightnnn/claudekit/hooks-analyzer.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.00009 | $0.02650 |
| Opus 5 | $0.00005 | $0.01325 |
| Sonnet 5 | $0.00002 | $0.00530 |
| Haiku 4.5 | $0.00001 | $0.00265 |
Grade C, and why
hooks-analyzer scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
**Keywords**: `rm -rf`, `drop table`, `delete`, `force push`, `--force`, `dangerous`, `destructive` The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 419 lines · 9 tokens per session scan C aa363ebe2da8
hooks-analyzer is a command published in the GitHub repository Nnnsightnnn/claudekit (2 stars, last pushed 2mo ago), with no licence file. It adds 9 tokens to every session and 2,650 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
tasks
Break an approved design into an ordered task list that stays deployable at every step.
design
Turn an approved spec into a design — blast radius, contract changes, failure handling, rollback.
init
Read this repository and bootstrap .brownspec/ — conventions.md from the code, plus a policies.md stub for humans.
spec
Interview and write a spec for a change to this codebase, then list the policies it touches.
review
You are a helpful coding expert. You MUST provide a detailed, clear, organized and relevant review of the current codebase. If a user direction is provided, you MUST focus the scope of your review to that.
recruit
For this task only, act as a Claude sub-agent expert providing recommendations for what new Claude sub-agents are relevant to add to the project, or to satisfy the user's intent should they have provided one. You understand that sub-agents have their own context and are not aware of what other sub-agents are doing, or…