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/paruff/uFawkesAIWrote 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/paruff/ufawkesai/implement)<a href="https://agentmods.dev/commands/paruff/ufawkesai/implement"><img src="https://agentmods.dev/badge/commands/paruff/ufawkesai/implement/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/paruff/ufawkesai/implement"><img src="https://agentmods.dev/badge/commands/paruff/ufawkesai/implement.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.00007 | $0.00077 |
| Opus 5.5 | $0.00003 | $0.00031 |
| Sonnet 5.5 | $0.00001 | $0.00015 |
| Haiku 4.5 | $0.00001 | $0.00008 |
Grade A, and why
implement 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 8d 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
Read the feature's docs/ai-sdlc/<feature>/plan.md first.
If missing, stop and instruct the user to run /plan.
Implement one phase at a time.
After each phase, run /verify gates.
Update the plan checklist.
Ask for checkpoint approval before proceeding.
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.
- 8d ago Changed 804bdba82cb5
- 14d ago Changed 58e4dfdcfeee
- 15d ago First seen · 11 lines · 7 tokens per session scan A 31b537eb552f
implement is a command published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed today), licensed MIT. It adds 7 tokens to every session and 77 once invoked, about $0.0000 per session on Opus 5.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-09-27.
Other commands, from other repositories
save-todo
../../workflows/save-todo.md.
route
../../workflows/route.md.
runners
../../workflows/runners.md.
seo-fanout
../../seo/seo-fanout.md.
project-recap
Generate a visual project recap for context switching.
project-init
Stand up the context layers for a project — a thin pointer-style AGENTS.md plus seed compass maps — without touching the memory layer.