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 skills/fmind/agent-evolutions/new-agent-evolutionnpx skills add fmind/agent-evolutions --skill new-agent-evolutiongit clone --depth 1 https://github.com/fmind/agent-evolutionsWhat 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.00074 | $0.01003 |
| Opus 5 | $0.00037 | $0.00502 |
| Sonnet 5 | $0.00015 | $0.00201 |
| Haiku 4.5 | $0.00007 | $0.00100 |
Grade A, and why
new-agent-evolution 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.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
new-agent-evolution
Capture a verifiable optimization brief for <title>. Writes nothing until the user explicitly agrees.
0. Pre-flight
Resolve the argument. If it matches an existing .agents/evolutions/<id>-*/ (pure integer id or slug fragment), stop with "Evolution <id> already exists. Run /run-agent-evolution <id> (or /apply-agent-evolution <id> if the winner is set)." This skill only seeds new evolutions.
Read-only setup: AGENTS.md, README.md, the user ask, any spec the ask points at. Identify project test/build/lint commands — candidate gates. Confirm the cwd is a git repo (git rev-parse --is-inside-work-tree) — variants default to git worktrees.
1. Dialog first
First-turn output is chat-only: clarifying questions and a draft brief inline. Don't create files until the user explicitly agrees ("looks good", "ship it", edits incorporated).
Five elements. Propose concrete answers; ask only when irreducible (cap at 5 questions).
- Objective. One sentence — "Optimize X for Y." Reject vague answers; insist on a measurable Y.
- Gates. Hard pass/fail shell commands (exit 0 = pass). 2–4 typical (
pnpm typecheck,pnpm test,cargo build, custom verifiers). A variant failing any gate is excluded from ranking. - Rubric. Numeric ranking dimensions (≥ 1, typically 1–3). Each:
direction(minimize | maximize),cmd, optionalextract(regex with one capture group, orwall_clock_seconds). Composite is the rank-normalized weighted mean across axes, recomputed on read. - Scope.
kind: worktree(default —git worktree add HEAD) orfiles(copy listed paths). Forworktree, listincludeinformationally so apply knows what to diff. Forfiles,includeis required.excludeblocks paths apply must not touch. - Budget.
max_variants(total),parallel(concurrent per generation; sets the learning cadence). Optionalmax_minutes,plateau_generations(early stop on no-improvement). Defaultparallel = ceil(max_variants / 5)so the loop runs ~5 generations.
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 · 48 lines · 74 tokens per session scan A 70c66db1e018
new-agent-evolution is a skill published in the GitHub repository fmind/agent-evolutions (1 stars, last pushed 3mo ago), licensed MIT. It adds 74 tokens to every session and 1,003 once invoked, about $0.0004 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-31.
Other skills, from other repositories
gofer-documentation
Write or update customer-facing delivery documentation and generate its PublicAPI-capped lineage diagram. Use for Markdown, requirements, architecture, decisions, plans, validation evidence, or documentation graphs in a Gofer workspace.
eai
Start or continue the EAI delivery pipeline.
lever-new
Start a new lever — discuss the ask in chat, then capture intent (Goal, Success sketch, Context, Open questions) as §Brief. Hands off via /lever .
lever-status
Inspect or cancel levers. List all (no arg), detail one (TL;DR + criteria + per-criterion events timeline), or cancel one with cancel [ ]. Never advances the chain.
lever-init
Bootstrap a repo for agent-levers. Creates .agents/levers/, wires CLAUDE.md/GEMINI.md to import AGENTS.md, writes an AGENTS.md skeleton when missing. Hands off via /lever-new.
lever
Advance an existing lever. Reads lever.yaml.step and runs the chain (plan → do → check → act → done) autonomously until it pauses or finishes.