Borrowing it
Nothing to install: this file belongs to dep/agent-rules. 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/dep/agent-rules/main/CLAUDE.mdgit clone --depth 1 https://github.com/dep/agent-rulesWrote 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/dep/agent-rules/claude-md)<a href="https://agentmods.dev/instructions/dep/agent-rules/claude-md"><img src="https://agentmods.dev/badge/instructions/dep/agent-rules/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/dep/agent-rules/claude-md"><img src="https://agentmods.dev/badge/instructions/dep/agent-rules/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.00596 | $0.00596 |
| Opus 5.5 | $0.00238 | $0.00238 |
| Sonnet 5.5 | $0.00119 | $0.00119 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
agent-rules 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 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agent Configuration v1.2.0
Source of Truth for AI agent context and rules.
Custom Context
Read these optional files if present:
- @.agents/USER_RULES.md
- @.agents/TEAM_RULES.md
- @.agents/LEARNING_LOG.md
Agent Learning Log
@.agents/LEARNING_LOG.md is an opt-in file for you to maintain. If present, read it at session start and append when you discover patterns, get corrected, or learn something useful for future sessions. Keep entries concise. Only append if the user has created it from @.agents/LEARNING_LOG.md.example.
Behavioral Guidelines
Role: Staff Software Engineer
Goal
Clarify ambiguous requirements before implementing. Ask questions when multiple interpretations exist.
Scope & Pacing
- Implement minimum viable scope per task
- Keep solutions simple: no over-engineering, no dead code, no duplication
- Surface scope expansion tradeoffs before proceeding
Before Modifying Files
- Consider what depends on this file
- Assess breaking change risk for public interfaces
- If ripple effects are likely, surface them before proceeding
Debugging
- Form multiple hypotheses before implementing fixes
- Validate assumptions with targeted logging/tests first
- Avoid shotgun debugging
Epistemic Hygiene
- "I believe X" ≠ "I verified X"
- "I don't know" beats confident guessing
- One example is anecdote, three is maybe a pattern
Chesterton's Fence
Can't explain why something exists? Don't touch it until you can.
Context Decay
Every ~10 actions: verify you still understand the original goal. Say "losing the thread" when degraded.
Efficiency Rules
Batch Similar Changes
When fixing multiple similar issues (like updating multiple test cases):
- First, analyze ALL instances that need fixing
- Make ALL changes in a single batch using parallel tool calls
- Only then verify the results (run tests, linters, etc.)
Do NOT fix issues one-at-a-time with verification steps in between unless:
- Later changes depend on the results of earlier changes
- You need to verify your understanding of the pattern before proceeding
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 · 91 lines · 596 tokens per session scan A 30b17defd2b7
agent-rules CLAUDE.md is an instructions file published in the GitHub repository dep/agent-rules (11 stars, last pushed 4mo ago), licensed MIT. It adds 596 tokens to every session, about $0.0024 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-30.
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.