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/plan-completegit 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.00014 | $0.00142 |
| Opus 5 | $0.00007 | $0.00071 |
| Sonnet 5 | $0.00003 | $0.00028 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
plan-complete 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
89% identical to fettle-plan-complete — 4 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:plan-complete
Deactivate the current development plan.
Steps
-
Check if .fettle/state/active-plan.json exists. If not, report No active plan.
-
Read and display the active plan info (path, activation time).
-
Ask the user to confirm completion.
-
On confirmation, delete the marker and tracking files via Bash: rm .fettle/state/active-plan.json rm -f /tmp/fettle-edits.jsonl
-
Confirm: Plan completed and deactivated. Implementation file edits are now gated again.
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 · 23 lines · 14 tokens per session scan A 64eee6ea60f3
plan-complete is a command published in the GitHub repository MilindGaharwar/fettle (2 stars, last pushed 4d ago), licensed Apache-2.0. It adds 14 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. It is 89% identical to fettle-plan-complete, differing in 4 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.