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/milindgaharwar/fettle/fettle-explaingit clone --depth 1 https://github.com/MilindGaharwar/fettleWrote 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/milindgaharwar/fettle/fettle-explain)<a href="https://agentmods.dev/commands/milindgaharwar/fettle/fettle-explain"><img src="https://agentmods.dev/badge/commands/milindgaharwar/fettle/fettle-explain.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 | $0.00012 | $0.00142 |
| Opus 5 | $0.00006 | $0.00071 |
| Sonnet 5 | $0.00002 | $0.00028 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
fettle-explain 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- explain — 97% identical, 5 lines differ
What it actually says
/fettle:explain
Explain why Fettle blocked or warned about the last edit.
Usage
When the user invokes /fettle:explain:
fettle explain
Shows for each decision:
- Which hook ran (PreToolUse, PostToolUse, Stop)
- Which file was checked
- Which tool found the issue (ruff, semgrep, or infrastructure error)
- The specific violation(s)
- How to fix or suppress
Helps users understand: "Was this a code quality issue or a Fettle bug?"
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.
- 3d ago First seen · 26 lines · 12 tokens per session scan A b3a8f740ee60
fettle-explain is a command published in the GitHub repository MilindGaharwar/fettle (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 12 tokens to every session and 142 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
corporate-launcher
Build a secure, branded, organization-specific launcher around an AI coding CLI (Claude Code, Codex CLI, Gemini CLI, Cursor, or Cline) so the user can.
kb-ingest
Ingest external material into Sources/ inside the bound project KB, then update registry, index, and daily note as needed.
aod.blueprint
Unified project setup & story generation — auto-detects new vs existing projects.
generate-role
Resolve a need to a domain-expert role (existing, new leaf, or new parent) and draft it via the AUTHORING.md pipeline, opening a PR.
iterate
Iteration delivery — delivery check + archive + commit & tag + bump version.
um-setup
First-run setup — point the plugin at your universal-memory server, verify it, save config.