Borrowing it
Nothing to install: this file belongs to alanshurafa/co-evolution. 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/alanshurafa/co-evolution/master/AGENTS.mdgit clone --depth 1 https://github.com/alanshurafa/co-evolutionWrote 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/alanshurafa/co-evolution/agents-md)<a href="https://agentmods.dev/instructions/alanshurafa/co-evolution/agents-md"><img src="https://agentmods.dev/badge/instructions/alanshurafa/co-evolution/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/alanshurafa/co-evolution/agents-md"><img src="https://agentmods.dev/badge/instructions/alanshurafa/co-evolution/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.02799 | $0.02799 |
| Opus 5.5 | $0.01120 | $0.01120 |
| Sonnet 5.5 | $0.00560 | $0.00560 |
| Haiku 4.5 | $0.00280 | $0.00280 |
Grade A, and why
co-evolution 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
For agents reading this repo
This repo implements the Bounce Protocol — a convention for structured iterative refinement between AI agents using in-document markers. If you are an agent invoked against documents in this repo, you should know how to read and emit these markers.
The two markers
[CONTESTED]— appears on its own line below text you disagree with. The note states the disagreement and proposes a concrete alternative. If you see one in a document you are editing, either resolve it (delete it after applying its alternative or rebutting it) or leave it for the next agent.[CLARIFY]— appears on its own line below ambiguous text. The note offers two interpretations or asks a question with a finite answer space. If you can disambiguate, do so and delete the marker.
Both markers auto-expire after 2 passes: on the final pass of any bounce, you must resolve every remaining marker and may not introduce new ones. This rule guarantees convergence.
Full spec: BOUNCE-PROTOCOL.md. Reference implementation: agent-bouncer/.
How to interact with this repo
- If you are invoked via
/co-evolutionorbash co-evolve-bouncer.sh, you are in the general-purpose co-evolution workflow for questions, drafts, plans, specs, arguments, and markdown refinement - If you are invoked via
/dev-review(Claude Code) orbash dev-review/codex/dev-review.sh(Codex), you are inside the bounce pipeline — your role (reviewer / composer) and pass number are passed to you in the prompt template - If you are invoked via
/codex-build, you are orchestrating a detached Codex build: the session plans and reviews, Codex executes in the background under--preset codex-build, and the session is woken at gates (seeskills/codex-build/) - If you are orchestrating via
--preset claude-build, Codex plans and reviews while Claude executes the build synchronously; this path hard-requiresclaudeCLI auth because Claude is the executor (seedev-review/codex/claude-build.md) - If you are invoked via
bash agent-bouncer/agent-bouncer.sh <doc>, you are bouncing a single markdown document — same protocol applies - If you are exploring the repo directly without an explicit role, treat the protocol section above as orientation, then read the project-context sections below for structure and conventions
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 Changed · -32 lines · -211 tokens per session 4dbb1522255d
- 2mo ago First seen · 188 lines · 3,010 tokens per session scan A 54367aaf97f7
co-evolution AGENTS.md is an instructions file published in the GitHub repository alanshurafa/co-evolution (4 stars, last pushed 29d ago), licensed MIT. It adds 2,799 tokens to every session, about $0.0112 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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.