Borrowing it
Nothing to install: this file belongs to shehryarsaroya/agent-eve. 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/shehryarsaroya/agent-eve/master/CLAUDE.mdgit clone --depth 1 https://github.com/shehryarsaroya/agent-eveWrote 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/shehryarsaroya/agent-eve/claude-md)<a href="https://agentmods.dev/instructions/shehryarsaroya/agent-eve/claude-md"><img src="https://agentmods.dev/badge/instructions/shehryarsaroya/agent-eve/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/shehryarsaroya/agent-eve/claude-md"><img src="https://agentmods.dev/badge/instructions/shehryarsaroya/agent-eve/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.09010 | $0.09010 |
| Opus 5 | $0.04505 | $0.04505 |
| Sonnet 5 | $0.01802 | $0.01802 |
| Haiku 4.5 | $0.00901 | $0.00901 |
Grade A, and why
agent-eve 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 9d 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 — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — AGENT EVE (né THE COMPACT, then AGENT TRANSFER)
Context file for any AI session in this repo. Written 2026-07-24, updated for SPEC v3.0. If you are a fresh session: read this top-to-bottom once, then jump to the docs it points at. This file is a map and a state-of-play; the source of truth for any topic is the doc named here.
0. 🚨 HARD RULES
- No secrets in this repo, ever. Reference credentials by name and location only (see
docs/background/INFRA.md). Never read, print, echo, or paste a secret value. Live keys exist in~/agentinsurance/game/.envand~/Projects/ideationjul3/yc-gstack-kit/credentials/.env— both are outside this repo and must stay there. - Deploy safely on the VPS. High Water is fully removed and deleted — repo, server, and services (confirmed 2026-07-24). There is nothing left to break, so the old "don't clobber it" rule is retired. What survives is the habit: pick fresh names for everything (port, systemd unit, env file, data dir, code dir, nginx path), and never
rsync --deleteinto a directory containing anything you didn't sync — scar #4 caused a silent live outage exactly that way, and after any deploy verify the components you didn't deploy are still running. - The design test. Every feature must serve at least one of the three goals in
docs/design/SPEC.md§1.1: watchable · autonomous · legible on screen. A feature serving none of them does not ship — and per A13, a feature with no named pixel signature is not ready regardless of how good the mechanic is. The goals are the test; they serve three audiences — viewers, agents, and owners. Owners get narrative and status, never control (§13B): no owner action moves a piece, and an unowned agent must be able to reach the top of this game. - One word per concept.
SPEC.md§3 is the vocabulary canon and it is a rules surface, not a style guide. Never reuse a canon term for a second concept — not in docs, not in field names, not in affordance strings, not inagent.md. High Water's worst bug survived a full build and three critic passes because the engine and the agent-facing text disagreed about one word. - Any gate priced in identities is unpriced (A15). Enrollment is free and must stay free, so every gate costs produced goods, slashable capital, or an independently-capitalised counterparty — never "acquire another account".
- Read before adding. ~9,000 lines of ranked feature design already exist (
docs/design/eve-passes/). Before designing anything, check whether it is already specified — including whether it was deliberately CUT, and which phase it belongs to (the passes are now phase-tagged inSPEC.md§0). - Parallel agents must never share an output file — nor a WORKING TREE. Concurrent writers thrash
and lose everything (this cost a full codex pass; see
docs/background/HIGH-WATER-LESSONS.mdscar #12).
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.
- 9d ago First seen · 345 lines · 9,010 tokens per session scan A b31c13446600
agent-eve CLAUDE.md is an instructions file published in the GitHub repository shehryarsaroya/agent-eve (11 stars, last pushed 1mo ago), licensed MIT. It adds 9,010 tokens to every session, about $0.0451 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 instructions, from other repositories
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.
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.