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/thettwe/nyannWrote 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/thettwe/nyann/explain-diff)<a href="https://agentmods.dev/commands/thettwe/nyann/explain-diff"><img src="https://agentmods.dev/badge/commands/thettwe/nyann/explain-diff/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/thettwe/nyann/explain-diff"><img src="https://agentmods.dev/badge/commands/thettwe/nyann/explain-diff.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.00055 | $0.00380 |
| Opus 5.5 | $0.00022 | $0.00152 |
| Sonnet 5.5 | $0.00011 | $0.00076 |
| Haiku 4.5 | $0.00006 | $0.00038 |
Grade A, and why
nyann:explain-diff 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
Plugin root: This is a Claude Code plugin, NOT a CLI tool. Do NOT
search via which, npm list, pip list, or brew list. This file
is at <plugin_root>/commands/. All scripts: <plugin_root>/bin/.
Read the matching skills/*/SKILL.md for the full flow.
/nyann:explain-diff
Wraps bin/explain-diff.sh. Read-only. Renders a DriftReport into
markdown (default) or DriftNarrative JSON (--format json).
Pairs with doctor: prefer bin/doctor.sh --explain over piping when
both are available, since doctor forwards the computed health score
and trend delta into the narrative header.
See skills/explain-diff/SKILL.md for severity mapping, output
shape, and when to read the output back to the user.
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 · 38 lines · 55 tokens per session scan A eb7c271e3d0f
nyann:explain-diff is a command published in the GitHub repository thettwe/nyann (7 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 380 once invoked, about $0.0002 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 commands, from other repositories
fix-pr-comments
Systematically resolve Pull Request review comments using gh CLI to fetch comments and apply requested changes.
cg-review
Review code against its call graph - reconstruct the implemented graph and diff it.
setup
Set up, configure, or reconfigure notabene and start the docs review server.
review
Command "review" from KhaiTrang1995/claude-code-structure, covering /project:review – code review command, usage, description, output format and shell step.
odoo-review
Review a GitHub PR against Odoo PSDU conventions — business need, file-by-file, then full-logic; before/after fixes; terminal-only, read-only.
odoo-review
Review a GitHub PR against Odoo PSDU conventions — business need, file-by-file, then full-logic; before/after fixes; terminal-only, read-only.