Evo is an agent plugin that turns a codebase into an automated experiment loop, discovering metrics, changing code, and testing whether those changes improve the results. It is used to optimize software through parallel subagents, tree-based exploration, shared experiment records, and optional regression or safety gates. The catalogue entries provide agent skills, hooks, commands, and other workflow components for operating Evo.
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/evo-hq/evoWrote 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/evo-hq/evo/optimize)<a href="https://agentmods.dev/commands/evo-hq/evo/optimize"><img src="https://agentmods.dev/badge/commands/evo-hq/evo/optimize/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/evo-hq/evo/optimize"><img src="https://agentmods.dev/badge/commands/evo-hq/evo/optimize.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.00011 | $0.00107 |
| Opus 5.5 | $0.00004 | $0.00043 |
| Sonnet 5.5 | $0.00002 | $0.00021 |
| Haiku 4.5 | $0.00001 | $0.00011 |
Grade A, and why
optimize 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.
What it actually says
Load and follow the evo optimize skill (named optimize under the evo plugin in your skill registry — use your skill loader, not a filesystem path). It drives the structured experiment loop: the orchestrator writes briefs and spawns subagents that own the candidate edits and runs.
Any arguments below are parameters for that skill (e.g. subagents=N, budget=N, autonomous).
$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.
- 1mo ago First seen · 11 lines · 11 tokens per session scan A 852fe68fbd10
optimize is a command published in the GitHub repository evo-hq/evo (1,486 stars, last pushed 22d ago), licensed Apache-2.0. It adds 11 tokens to every session and 107 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-08-30.
Other commands, from other repositories
run-autoresearch
Run an autonomous experiment loop via the Autoresearch Orchestrator agent.
orchestrate
This tool coordinates Claude Code's actions. It does NOT write code or create content.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
performance-bottlenecks
Identify and resolve performance bottlenecks in your development workflow.
review
Review proposed ADRs for lifecycle progression — accept implemented decisions, deprecate stale ones, archive trivial ones.
types
Debug and fix TypeScript type errors with systematic analysis and expert guidance.