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/qualitygit 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.00012 | $0.00156 |
| Opus 5 | $0.00006 | $0.00078 |
| Sonnet 5 | $0.00002 | $0.00031 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
quality 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.
What it actually says
Run fettle check --all (pass any additional arguments from $ARGUMENTS).
Present the results to the user, grouped by severity. If there are errors, suggest specific fixes based on the rule messages. If a baseline is available, highlight only new findings.
After presenting results, offer to:
- Fix the errors automatically (if any) with
fettle check --fix - Update the baseline with
fettle baseline update - Run a cross-review with
python3 -m fettle.cross_review
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 · 17 lines · 12 tokens per session scan A 7e979ec9f921
quality is a command published in the GitHub repository MilindGaharwar/fettle (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 12 tokens to every session and 156 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.
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.
aod.blueprint
Unified project setup & story generation — auto-detects new vs existing projects.
maintainer
Meta-skill that loads all llmwiki governance docs and exposes the three maintainer slash commands.
ox-session-pause
belongs in the ox CLI JSON output (guidance field), not here. Skills are agent-specific wrappers; ox serves all agents (Codex, etc.). --> Suspend the current session recording. Local cache continues to receive entries, but the upload at stop time will exclude the suspended range.
setup_research_plan
Set up or start a research project.