Borrowing it
Nothing to install: this file belongs to smbochkarev1/claude-code-playbook. 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/smbochkarev1/claude-code-playbook/main/CLAUDE.mdgit clone --depth 1 https://github.com/smbochkarev1/claude-code-playbookWrote 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/smbochkarev1/claude-code-playbook/claude-md)<a href="https://agentmods.dev/instructions/smbochkarev1/claude-code-playbook/claude-md"><img src="https://agentmods.dev/badge/instructions/smbochkarev1/claude-code-playbook/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/smbochkarev1/claude-code-playbook/claude-md"><img src="https://agentmods.dev/badge/instructions/smbochkarev1/claude-code-playbook/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.00852 | $0.00852 |
| Opus 5.5 | $0.00341 | $0.00341 |
| Sonnet 5.5 | $0.00170 | $0.00170 |
| Haiku 4.5 | $0.00085 | $0.00085 |
Grade A, and why
claude-code-playbook 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 2mo 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Drop-in template. Replace the
<...>placeholders and delete what you don't need. This file is prompt, not documentation — keep it short, imperative, and specific. Vague rules get ignored.
Who you're working with
- Role:
<e.g. product manager / staff engineer> - Stack you'll touch most:
<languages, key tools> - Preferences:
<terse answers? show diffs? ask before X?>
Workflow orchestration
1. Plan Mode by default
- Enter plan mode for any non-trivial task (3+ steps or an architectural decision).
- If something goes sideways, STOP and re-plan — don't keep pushing a broken approach.
- Write the spec before the code. Ambiguity resolved up front is cheaper than a wrong build.
2. Subagents keep the main context clean
- Offload research, exploration, and parallel analysis to subagents. One task per subagent.
- Throw more compute at hard problems via parallel agents, then synthesize.
- The main thread holds the conclusion, not the raw file dumps.
3. Self-improvement loop
- After ANY correction from me: append the pattern to
tasks/lessons.md. - Write a rule for yourself that prevents the same mistake. Review lessons at session start.
4. Verify before "done"
- Never mark a task complete without proving it works: run it, diff behavior, read the logs.
- Ask: "would a staff engineer approve this?"
5. Demand elegance (balanced)
- For non-trivial changes, pause: "is there a more elegant way?" If a fix feels hacky, redo it properly.
- Skip this for obvious one-liners — don't over-engineer.
6. Autonomous bug fixing
- Given a failure (log, error, red test): fix the root cause. No hand-holding required, no temporary patches.
Task management
- Plan first → write checkable items to
tasks/todo.md. - Verify the plan with me before implementing.
- Track progress — check items off as you go.
- Explain — high-level summary at each step.
- Capture lessons — update
tasks/lessons.mdafter corrections.
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.
- 2mo ago First seen · 70 lines · 852 tokens per session scan A 5cb68c3ed614
claude-code-playbook CLAUDE.md is an instructions file published in the GitHub repository smbochkarev1/claude-code-playbook (2 stars, last pushed 3mo ago), licensed MIT. It adds 852 tokens to every session, about $0.0034 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.