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/evomap/evolver-claude-code-plugin/rungit clone --depth 1 https://github.com/EvoMap/evolver-claude-code-pluginWhat 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.00024 | $0.00278 |
| Opus 5 | $0.00012 | $0.00139 |
| Sonnet 5 | $0.00005 | $0.00056 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
run 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
Run an Evolver evolution cycle in the current git repository.
Steps:
- Confirm we're in a git repo (
git rev-parse --is-inside-work-tree). If not, tell the user Evolver requires git and stop. - Resolve the CLI and run it, passing through the user's flags. Execute:
EVOLVER="evolver"; command -v evolver >/dev/null 2>&1 || EVOLVER="npx -y @evomap/evolver"
EVOLVE_STRATEGY="${EVOLVE_STRATEGY:-balanced}" $EVOLVER run $ARGUMENTS
- Summarize what changed: which signals were collected, which gene was selected/mutated, and whether any changes are now pending solidify. If changes are pending, remind the user they can inspect and accept them with
/evolver:review(or roll back with/evolver:review --reject).
Do not auto-approve pending changes — leave that to the user via /evolver:review.
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 · 21 lines · 24 tokens per session scan A eb27ef01bdcc
run is a command published in the GitHub repository EvoMap/evolver-claude-code-plugin (12 stars, last pushed 12d ago), licensed MIT. It adds 24 tokens to every session and 278 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-30.
Other commands, from other repositories
learn
Force claude-smart to extract learnings from this session now.
component
Scaffold a new React component grounded in the paper-mono primitives. Requires explicit kind or a nearest-existing-component match. No empty divs, no speculative scaffolding.
memory-store
Store an insight, decision, or pattern to memory.
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
no-vibe
Enter no-vibe mode in OpenCode (tutor mode, no direct project file writes).
teach-me-testing
Teach testing progressively through structured sessions. Use when user says ""lets learn testing"" or ""I want to study test practices"".