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/mickeyyaya/evolve-loop/plan-reviewgit clone --depth 1 https://github.com/mickeyyaya/evolve-loopWrote 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/mickeyyaya/evolve-loop/plan-review)<a href="https://agentmods.dev/commands/mickeyyaya/evolve-loop/plan-review"><img src="https://agentmods.dev/badge/commands/mickeyyaya/evolve-loop/plan-review.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.00064 | $0.00148 |
| Opus 5 | $0.00032 | $0.00074 |
| Sonnet 5 | $0.00013 | $0.00030 |
| Haiku 4.5 | $0.00006 | $0.00015 |
Grade A, and why
plan-review 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 today.
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 the plan-review skill from the evo plugin (Skill tool id evo:plan-review); follow its SKILL.md instructions exactly.
Arguments: $ARGUMENTS
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.
- today First seen · 11 lines · 64 tokens per session scan A d967017643ac
plan-review is a command published in the GitHub repository mickeyyaya/evolve-loop (5 stars, last pushed today), licensed Apache-2.0. It adds 64 tokens to every session and 148 once invoked, about $0.0003 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-09-03.
Other commands, from other repositories
brooks-debt
Run a Brooks-Lint tech debt assessment.
plan
Turn an approved spec into an implementation plan an engineer with zero context could execute — with a quality controller that blocks placeholders and hollow tasks.
audit
Onboard an existing codebase: every domain's checks over the whole tree, then a triaged plan to bring it in line.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
sync
Reconcile coco tracker state with the configured issue tracker. Syncs task statuses and reports mismatches.