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/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/plan-complete)<a href="https://agentmods.dev/commands/milindgaharwar/fettle/plan-complete"><img src="https://agentmods.dev/badge/commands/milindgaharwar/fettle/plan-complete/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/milindgaharwar/fettle/plan-complete"><img src="https://agentmods.dev/badge/commands/milindgaharwar/fettle/plan-complete.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.00014 | $0.00146 |
| Opus 5.5 | $0.00006 | $0.00058 |
| Sonnet 5.5 | $0.00003 | $0.00029 |
| Haiku 4.5 | $0.00001 | $0.00015 |
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 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.
This is a copy
89% identical to fettle-plan-complete — 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:plan-complete
Deactivate the current development plan.
Steps
-
Run
fettle plan statusand show the active checklist. If none exists, report that and stop. -
If any checklist items remain unchecked, show them and stop. Use
fettle plan check <text>as work is completed. -
Ask the user to confirm completion.
-
On confirmation, archive the completed plan through the canonical CLI:
fettle plan complete -
Run
fettle plan statusand confirm that no active session plan remains.
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 Changed · +1 lines 198d3c7bf295
- 1mo ago First seen · 23 lines · 14 tokens per session scan A 64eee6ea60f3
plan-complete is a command published in the GitHub repository MilindGaharwar/fettle (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 14 tokens to every session and 146 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to fettle-plan-complete, differing in 5 lines, and is treated as a copy.
Other commands, from other repositories
aitask-pickrem
Pick and implement a task in remote/non-interactive mode. All decisions from execution profile - no AskUserQuestion calls.
aitask-trail
Create, refresh, or show an implementation trail — a durable, wave-structured, evidence-backed task-sequencing artifact stored via ait artifact.
aitask-wrap
Wrap uncommitted changes into an aitask with retroactive documentation and traceability.
aitask-run-gates
Run a task's declared gates — the conversational front of the headless gate orchestrator engine. Dispatches unlocked machine-gate verifiers within their retry budgets, observes human gates without self-signalling, and reports.
aitask-add-model
Register a known code-agent model in models .json, optionally promote it to default across config/seed/DEFAULTAGENTSTRING.
aitask-reviewguide-import
Import external content (file, URL, or repository directory) as a reviewguide with proper metadata.