Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/awattar/claude-code-best-practices/claude-mdgit clone --depth 1 https://github.com/awattar/claude-code-best-practicesWrote 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/awattar/claude-code-best-practices/claude-md)<a href="https://agentmods.dev/instructions/awattar/claude-code-best-practices/claude-md"><img src="https://agentmods.dev/badge/instructions/awattar/claude-code-best-practices/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.02327 | $0.02327 |
| Opus 5 | $0.01163 | $0.01163 |
| Sonnet 5 | $0.00465 | $0.00465 |
| Haiku 4.5 | $0.00233 | $0.00233 |
Grade A, and why
claude-code-best-practices 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 6d 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 — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Best Practices - Project Guide
Overview
This is a documentation repository focusing on Claude Code best practices, patterns, and real-world usage examples. The project serves as a comprehensive guide for developers looking to integrate Claude Code into their terminal-based coding workflows effectively.
Project Type
Documentation / Knowledge Repository with Custom Claude Code Commands.
Quick Start
# Clone the repository
git clone <repository-url>
cd claude-code-best-practices
# Read the main documentation
cat README.md
# View available custom commands
ls .claude/commands/
# Get help with custom commands
/help-commands # View all available commands and usage
# Use custom commands (examples)
/commit # Create conventional commits
/custom-init # Initialize CLAUDE.md for any project
/issue <number> # Work on GitHub issues
/reviewpr <number> # Review pull requests
/test <scope> # Run and improve tests
Architecture
Project Structure
claude-code-best-practices/
├── LICENSE # MIT License
├── README.md # Main documentation with best practices
├── .gitmessage # Git commit message template
├── .github/ # GitHub templates and workflows
│ ├── pull_request_template.md # Standardized PR template
│ └── COMMIT_CONVENTION.md # Commit best practices guide
└── .claude/ # Claude Code configuration
├── settings.json # Permissions + hooks (project scope)
├── commands/ # Custom slash commands
│ ├── commit.md # Conventional commit helper
│ ├── custom-init.md # CLAUDE.md generation command
│ ├── help-commands.md # Command help and usage guide
│ ├── issue.md # GitHub issue workflow
│ ├── reviewpr.md # Pull request review tool
│ └── test.md # Test suite management
├── agents/ # Specialized AI agents
│ ├── general-backend-developer.md
│ ├── general-code-quality-debugger.md
│ ├── general-devops.md
│ ├── general-frontend-developer.md
│ ├── general-fullstack-developer.md
│ ├── general-pm.md
│ ├── general-qa.md
│ ├── general-solution-architect.md
│ ├── general-technical-project-lead.md
│ └── general-technical-writer.md
└── skills/ # Model-invoked skills
└── conventional-commits/
└── SKILL.md # Auto-enforces commit convention
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.
- 6d ago First seen · 274 lines · 2,327 tokens per session scan A e0e383eb7a84
claude-code-best-practices CLAUDE.md is an instructions file published in the GitHub repository awattar/claude-code-best-practices (251 stars, last pushed 3mo ago), licensed MIT. It adds 2,327 tokens to every session, about $0.0116 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
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).
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.
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.
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 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).