Borrowing it
Nothing to install: this file belongs to mickeyyaya/evolve-loop. 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/mickeyyaya/evolve-loop/main/CLAUDE.mdgit clone --depth 1 https://github.com/mickeyyaya/evolve-loopWrote 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/mickeyyaya/evolve-loop/claude-md)<a href="https://agentmods.dev/instructions/mickeyyaya/evolve-loop/claude-md"><img src="https://agentmods.dev/badge/instructions/mickeyyaya/evolve-loop/claude-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/mickeyyaya/evolve-loop/claude-md"><img src="https://agentmods.dev/badge/instructions/mickeyyaya/evolve-loop/claude-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.04583 | $0.04583 |
| Opus 5.5 | $0.01833 | $0.01833 |
| Sonnet 5.5 | $0.00917 | $0.00917 |
| Haiku 4.5 | $0.00458 | $0.00458 |
Grade A, and why
evolve-loop CLAUDE.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 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Instructions (Claude Code)
Read AGENTS.md first. It has the cross-CLI invariants and the 12 Core Agent Rules. This file is the Claude Code overlay (a digest).
The full runtime detail is in docs/operations/runtime-reference.md: the env-var table, the operator commands, the ship classes and the publish pipeline. Read it before you change loop behavior, flags, gates or releases. Release notes: CHANGELOG.md.
Operating policy (canonical, environment-independent): docs/operations/operating-policy.md. A pipeline issue gets a console-first fix at maximum reasoning. Routing is typed plumbing. Salvage comes before requeue. Wiring proofs are mandatory. The repo, not session memory, is the source of truth for these rules.
Automation Loop Guardrails
- When you run the evolve loop or any batch/merge-train automation, evaluate the output after EVERY cycle. If 2 consecutive cycles produce zero ships (0 merged PRs), STOP the loop immediately. Find the root cause in the pipeline before you run another wave. The canonical zero-ship halt rule is an operator guardrail, not a compiled breaker: docs/operations/operating-policy.md §4.1.
- Never let a batch run more than 2 unproductive waves "to see if it self-corrects".
- ADR-0072 reconciliation: a zero-ship streak is evidence of a SYSTEM fail, so HALT + P0 applies. This does not conflict with "never stop the queue". That rule governs task-level failures.
Status Reporting
When you report on a batch or a pipeline run, always include these items:
- the cycles that ran;
- the ships or lanes that completed (for example, 2/2);
- the open PR numbers;
- the names of the failed CI jobs, with the failure class;
- the specific next action.
Do not report "running" or "in progress" as a status without these numbers.
Session conventions
- Confirm direction first: multi-step or multi-cycle work needs a 3-bullet plan and an approval. These tasks are exempt: single-cycle bug fixes, tasks that specify a file path, and tasks from an approved plan.
- Output discipline: give summaries with
file:linerefs. Put findings of more than 300 lines in a markdown file, not in the chat. - Jobs that run for a long time: after the launch, verify the health (exit codes, log tail). Make a checkpoint every cycle so that
--resumeworks. Report failures immediately. - Pre-commit review fleet: change → code-simplifier → (architecture-reviewer ∥ code-reviewer, parallel, both read-only) → address the findings → commit.
- architecture-reviewer (.claude/agents/architecture-reviewer.md) blocks the commit: you must fix each CRITICAL finding (by the rubric of the profile) before the commit.
- A pure-docs diff skips the architecture-reviewer, but not the commit gate. The commit gate still requires the simplify and review capabilities. One
code-review-simplifydiff-review pass covers both (ADR-0115). - Only a proven comment removal needs no reviewer.
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 Changed · +3 lines · +219 tokens per session b52d9201a6cf
- 3d ago Changed · +3 lines · +159 tokens per session 07ff52ea08bf
- 4d ago Changed · +46 tokens per session 29d3bc691893
- 9d ago Changed · +1 lines · +59 tokens per session eee573163cf0
- 12d ago Changed · +8 lines · +368 tokens per session 37a259ed3ab5
- 13d ago Changed · +63 lines · +733 tokens per session ea5c65dc7bb6
- 14d ago Changed · +345 tokens per session 5e67203dda19
- 20d ago Changed · +1 lines · +64 tokens per session eb7d76ac0496
- 21d ago Changed · +65 tokens per session 21050f0911c0
- 24d ago First seen · 81 lines · 2,525 tokens per session scan A bab687ebe3c9
evolve-loop CLAUDE.md is an instructions file published in the GitHub repository mickeyyaya/evolve-loop (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 4,583 tokens to every session, about $0.0183 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.