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-plan-activategit 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-plan-activate)<a href="https://agentmods.dev/commands/milindgaharwar/fettle/fettle-plan-activate"><img src="https://agentmods.dev/badge/commands/milindgaharwar/fettle/fettle-plan-activate.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.00010 | $0.00583 |
| Opus 5 | $0.00005 | $0.00292 |
| Sonnet 5 | $0.00002 | $0.00117 |
| Haiku 4.5 | $0.00001 | $0.00058 |
Grade A, and why
fettle-plan-activate 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 4d 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:
- plan-activate — 98% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fettle:plan-activate
Activate a development plan to unlock implementation file edits.
Steps
-
Ask the user which plan file to activate. If they provide a path, use it. If not, search for
.mdfiles indocs/plans/and present the list. -
Read the plan file completely.
-
Run the structural validator:
python3 -m fettle.plan_validator <PLAN_PATH>If it fails, report every error verbatim and do NOT activate. The errors name the exact WP and missing method type. Fix the plan first.
-
Check for adversarial review:
- Look for a
## Council Reviewor## Adversarial Reviewsection in the plan, OR - Check if a council report file is referenced in the plan header (e.g.,
council_report: /path/to/report.md) - If neither exists: WARN the user that no adversarial review is on record. For plans with implementation tasks, recommend an adversarial review pass (a second model or a colleague red-teaming the plan) before activation. Strongly recommended but does not hard-block.
- Look for a
-
If validation passes, write the marker file:
echo '{"plan": "<PLAN_PATH>", "approved": true, "ts": <UNIX_TIMESTAMP>}' > .fettle/state/active-plan.json -
Confirm activation:
Plan activated: <plan name> Path: <plan path> Work packages: <count> Implementation file edits are now allowed.
Validation rules enforced (plan_validator.py)
Every WP containing at least one implementation method task (TDD, BUILD, FIX, REFACTOR, CODE, INTEGRATION) must also contain:
| Required method | What it checks |
|---|---|
| TDD | Unit tests written before implementation |
| INTEGRATION | End-to-end test against the running system |
| REGRESSION | Named failure scenario (must cite incident/bug -- generic "regression test" is blocked) |
| LIVE | Exact command + observable outcome (must include an actual command -- "verify it works" is blocked) |
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.
- 4d ago First seen · 62 lines · 10 tokens per session scan A 81424f4f3e0b
fettle-plan-activate is a command published in the GitHub repository MilindGaharwar/fettle (2 stars, last pushed today), licensed Apache-2.0. It adds 10 tokens to every session and 583 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.
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.
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.
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.