Borrowing it
Nothing to install: this file belongs to fmind/agent-evolutions. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fmind/agent-evolutions/main/AGENTS.mdgit clone --depth 1 https://github.com/fmind/agent-evolutionsWrote 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/instructions/fmind/agent-evolutions/agents-md)<a href="https://agentmods.dev/instructions/fmind/agent-evolutions/agents-md"><img src="https://agentmods.dev/badge/instructions/fmind/agent-evolutions/agents-md/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/instructions/fmind/agent-evolutions/agents-md"><img src="https://agentmods.dev/badge/instructions/fmind/agent-evolutions/agents-md.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.01319 | $0.01319 |
| Opus 5.5 | $0.00528 | $0.00528 |
| Sonnet 5.5 | $0.00264 | $0.00264 |
| Haiku 4.5 | $0.00132 | $0.00132 |
Grade A, and why
agent-evolutions AGENTS.md 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.
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.
AGENTS.md
Overview
- agent-evolutions ships three slash-command skills —
/new-agent-evolution,/run-agent-evolution,/apply-agent-evolution— that together drive a coding agent through a genetic exploration loop: gather a verifiable objective, generate variants in parallel batches, learn from each generation, pick the winner by exit codes and numeric rubric, port the winner into the repo. One skill per phase (Capture / Run / Apply); each refuses to operate outside its phase based onevolution.yamlfield presence. - Skills are file-based and harness-agnostic: the same
skills/tree works in Claude Code, Gemini CLI, GitHub Copilot, and OpenCode. - End-user state lives in
.agents/evolutions/<id>-<slug>/:evolution.yaml(machine state, validated againstevolution.schema.json),EVOLUTION.md(single human/agent surface — TL;DR, Brief, Variants, Results; the §Brief section is loaded verbatim by every variant sub-agent),variants/v<n>/workspace/(per-variant isolated checkout or file copy),variants/v<n>/result.json(sub-agent output, validated againstresult.schema.json). - State is derived from field presence, not an explicit step machine: empty
variants[]= ready (run/new-agent-evolutionfirst); has variants but nowinner= running; haswinnerbut noapplied= evaluated; hasapplied= done. Each skill checks reality on entry and refuses if invoked in the wrong phase — nostepenum, nopauseflag.
Conventions
-
Line caps. Skill files load into agent context on every run; verbosity directly costs context budget. Targets:
skills/<name>/SKILL.md— ≤ 100 lines per file (each phase skill is self-contained).- Project-root markdown (
README.md,AGENTS.md) — uncapped, but tighten when it sprawls.
When the file approaches its cap, prefer cutting motivational/explanatory prose over removing structural rules. Each rule should be stated once, in the imperative, in the file the agent loads when it needs it. The "why" lives in commit messages and PR descriptions.
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 · 48 lines · 1,319 tokens per session scan A 2975df656eb1
agent-evolutions AGENTS.md is an instructions file published in the GitHub repository fmind/agent-evolutions (1 stars, last pushed 4d ago), licensed MIT. It adds 1,319 tokens to every session, about $0.0053 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-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.