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/explaingit clone --depth 1 https://github.com/MilindGaharwar/fettleWhat 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.00000 | $0.00117 |
| Opus 5 | $0.00000 | $0.00059 |
| Sonnet 5 | $0.00000 | $0.00023 |
| Haiku 4.5 | $0.00000 | $0.00012 |
Grade A, and why
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 2d 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.
This is a copy
97% identical to fettle-explain — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 2d ago First seen · 21 lines · 0 tokens per session scan A 071056475413
explain is a command published in the GitHub repository MilindGaharwar/fettle (2 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 117 tokens. A static security scan graded it A with 0 findings. It is 97% identical to fettle-explain, differing in 5 lines, and is treated as a copy.
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.
send
Send a message to a running agent session. Use this to correct or direct a live agent mid-stream without killing and respawning it.
ox-session-review
Command "ox-session-review" from sageox/ox, covering failure-mode watch-list (read first), from the ledger root. should print 0, phase 1 — scan & score (read-only), quality buckets (first match wins) and removal candidates.
continue
Generate session handoff file for seamless work resumption.
release
Walk the llmwiki release process step by step.
ox-conversation
pinning, errors) belongs in the ox CLI JSON output (guidance field) and ox guide conversations, not here. Skills are agent-specific wrappers; ox serves all agents (Codex, etc.). --> Read recorded team conversations locally: list, summaries, distillation topics, and transcript slices.