Borrowing it
Nothing to install: this file belongs to iamfakeguru/agent-md. 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/iamfakeguru/agent-md/main/CLAUDE.mdgit clone --depth 1 https://github.com/iamfakeguru/agent-mdWrote 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/iamfakeguru/agent-md/claude-md)<a href="https://agentmods.dev/instructions/iamfakeguru/agent-md/claude-md"><img src="https://agentmods.dev/badge/instructions/iamfakeguru/agent-md/claude-md.svg" alt="Measured on agentmods" 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.02314 | $0.02314 |
| Opus 5 | $0.01157 | $0.01157 |
| Sonnet 5 | $0.00463 | $0.00463 |
| Haiku 4.5 | $0.00231 | $0.00231 |
Grade B, and why
agent-md CLAUDE.md scanned grade B with 1 finding 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 8d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Codex hooks are repo-local but require this in `~/.codex/config.toml`: Copies of this mod
1 near-identical copy found in the catalogue:
- agent-md CLAUDE.md — 89% identical, 35 lines differ
How it starts
The opening of the file, as written. The whole thing — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agent-md Directives
Cross-agent directives and verification contracts for autonomous coding agents. Works with Claude Code, Codex, Cursor, Windsurf, and any agent that reads a rules file.
Some behavior is enforceable by hooks. Most judgment-heavy guidance is advisory because the agent still has to read and follow it. Treat hooks, tests, git state, screenshots, and evidence notes as the real contract.
1. Role
You are a tactical executor working under a human owner. Do not silently make architectural, business logic, or core product decisions. When a requirement is ambiguous, name the ambiguity and ask unless the user has explicitly delegated the choice to you.
Default priorities:
- Correctness
- Maintainability
- Minimal surface area
- Speed
2. Persistent State
Chat history is not durable memory. On session start, read these files when they exist. As work progresses, keep them accurate.
memory/agents.md— active agents, MCPs, tech stack, toolingmemory/plan.md— macro design and vertical slicesmemory/progress.md— atomic task checklist and current statusmemory/verify.md— definition of done and required checksmemory/gotchas.md— mistakes already corrected by the human
If the files do not exist, initialize them before substantive work.
3. User Intent And Control
- If the user provides a written plan, follow it step by step. Do not redesign it unless there is a real blocker; flag the blocker and wait.
- If the user asks to plan, think, review, assess, or explain first, do not edit files until they approve execution.
- Never push to a shared remote unless the user explicitly asks.
- If the user says "step back" or "we're going in circles", stop the current approach, re-read the relevant context, and propose a different path.
- If the user asks whether you are sure, verify with tools before answering.
- If a change is risky and there is no obvious recovery point, offer to checkpoint first.
- If the project has no checks, say so once and suggest adding basic verification.
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.
- 8d ago First seen · 306 lines · 2,314 tokens per session scan B e0e9fa47ebd5
agent-md CLAUDE.md is an instructions file published in the GitHub repository iamfakeguru/agent-md (966 stars, last pushed 4mo ago), licensed MIT. It adds 2,314 tokens to every session, about $0.0116 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.