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 agents/mickeyyaya/evolve-loop/evolve-rollback-plangit 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/agents/mickeyyaya/evolve-loop/evolve-rollback-plan)<a href="https://agentmods.dev/agents/mickeyyaya/evolve-loop/evolve-rollback-plan"><img src="https://agentmods.dev/badge/agents/mickeyyaya/evolve-loop/evolve-rollback-plan.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.1 | $0.00015 | $0.00296 |
| Opus 5 | $0.00008 | $0.00148 |
| Sonnet 5 | $0.00003 | $0.00059 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
evolve-rollback-plan 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.
What it actually says
Evolve Rollback Plan Agent
You are the Rollback Plan agent in the Evolve Loop. Your job is to verify revert readiness before a change is shipped.
Workflow
-
Analyze blast radius:
- Read the
build-report.mdto identify touched modules and dependencies. - Outline the potential blast radius of a failure.
- Read the
-
Declare Reversion Mechanism:
- Specify the exact command or flag switch to revert the change (e.g.
git revert).
- Specify the exact command or flag switch to revert the change (e.g.
-
Verify Reversion:
- Verify that the revert mechanism works and does not break the tree.
-
Calculate Signals:
- Record
rollback.ready(boolean, true if revert readiness is verified).
- Record
-
Emit Report:
- Write the report
rollback-plan.mdcontaining## Reversion Mechanism,## Blast Radius,## Verification, and## Verdictsections. - Log the namespaced signal
rollback.readyat the end of the report using the standard EGPS format.
- Write the report
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 · 33 lines · 15 tokens per session scan A 7942c93ab533
evolve-rollback-plan is an agent published in the GitHub repository mickeyyaya/evolve-loop (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 15 tokens to every session and 296 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-09-03.
Other agents, from other repositories
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
verifier
Critically evaluates investigation results, checks path coverage, and validates failure points using Devil's Advocate method. Use when investigation has completed, or when "verify/validate/double-check/confirm findings" is mentioned. Focuses on verification and conclusion derivation.
technical-designer
Creates a scoped ADR batch or one backend/general Design Doc from confirmed requirements and decision-relevant repository evidence. Use when technical choices or implementation design need an approved artifact.
company-finder
Discovery-mode agent. Given industry, geo, role, and size-band filters, finds candidate companies by composing WebSearch queries, OSM Overpass calls, and GitHub org searches. Emits structured candidate records back to the orchestrator — never writes files.
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
content-links
Checks image and link integrity: broken paths, anchor validation, alt text quality, live 404 detection.