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/JordanGunn/nunchuckWrote 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/jordangunn/nunchuck/sniff-bloaters)<a href="https://agentmods.dev/commands/jordangunn/nunchuck/sniff-bloaters"><img src="https://agentmods.dev/badge/commands/jordangunn/nunchuck/sniff-bloaters/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/commands/jordangunn/nunchuck/sniff-bloaters"><img src="https://agentmods.dev/badge/commands/jordangunn/nunchuck/sniff-bloaters.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.00000 | $0.00106 |
| Opus 5 | $0.00000 | $0.00053 |
| Sonnet 5 | $0.00000 | $0.00021 |
| Haiku 4.5 | $0.00000 | $0.00011 |
Grade A, and why
sniff-bloaters 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
sniff-bloaters
Detect bloaters smells (Long Method, Large Class, Long Parameter List) using deterministic heuristics and append findings to .sniff/findings.jsonl.
This command delegates to the agent skill at skills/sniff/sniff-bloaters/.
Skill Root
- Path:
skills/
Skill Location
- Path:
skills/sniff/sniff-bloaters/ - Manifest:
skills/sniff/sniff-bloaters/SKILL.md
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 · 0 tokens per session scan A 234fb6011d3d
sniff-bloaters is a command published in the GitHub repository JordanGunn/nunchuck (9 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 106 tokens. 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
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
debug-pod
Debug a failing or unhealthy Kubernetes pod by analyzing events, logs, and configuration.
map
Generate a dependency map showing how modules and files relate to each other in the codebase.
root-cause
Use when any test fails, bug appears, or behaviour surprises you, before proposing a fix - find the cause and prove it, by reading real evidence, tracing bad values back to their origin, comparing against a working case, and testing one hypothesis at a time.
find-dead-code
Identify unused code across the codebase.
verify
Run the full verification suite (build, type-check, tests, lint) via a fresh-context verification-runner subagent; reports evidence paths. Read-only by default; opt-in '--fix' runs a bounded auto-fix loop (max 2 cycles). Use before marking featurelist.json status as 'pass'.