Borrowing it
Nothing to install: this file belongs to ayi-ai/vibe-coding-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/ayi-ai/vibe-coding-playbook/main/CLAUDE.mdgit clone --depth 1 https://github.com/ayi-ai/vibe-coding-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/ayi-ai/vibe-coding-playbook/claude-md)<a href="https://agentmods.dev/instructions/ayi-ai/vibe-coding-playbook/claude-md"><img src="https://agentmods.dev/badge/instructions/ayi-ai/vibe-coding-playbook/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.00485 | $0.00485 |
| Opus 5 | $0.00243 | $0.00243 |
| Sonnet 5 | $0.00097 | $0.00097 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
vibe-coding-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 7d 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineering discipline (obey before writing any code)
Drop-in rules for AI coding agents. Adapted from Andrej Karpathy's observations (github: multica-ai/andrej-karpathy-skills), plus a task-tier and a one-feature-loop rule.
Tier the task first
- Small change (typo / styling / one-line fix): just do it — no process, no docs — but obey the disciplines below.
- Real product (shipped / maintained / for others): align on the need first; never generate a whole system in one shot.
Think before coding
- Don't guess on my behalf. When a request is ambiguous, present the interpretations and let me choose — don't silently pick one and run.
- If there's a simpler approach, say so. If you're confused or stuck, stop and name what's unclear.
Simplicity first
- Write the least code that solves the problem. No unrequested abstraction, configurability, or flexibility.
- No error handling for impossible scenarios. If 200 lines could be 50, rewrite it.
Surgical changes
- Change only the files and functions I named. No drive-by "improvements", refactors, or dependency upgrades.
- Every changed line must trace to my request. Mention unrelated dead code — don't delete it.
- In existing code: match the current style (even if you'd do it differently); only clean up imports/variables your change orphaned, leave pre-existing old code alone.
One feature at a time
- Don't generate a whole system at once. Take one feature through its smallest working loop, test it, then move on.
- Remind me to commit after each working feature.
Goal-driven
- Turn "fix the bug" into "write a failing test that reproduces it, then make it pass."
- State explicit pass/fail criteria, then loop on your own until they're met.
Docs before code (real products only)
- For a real product, don't write feature code without PRD / architecture / status docs; when requirements change, update docs before code.
- Small changes and personal tools can skip this.
Communication
- Match my level: terse if I'm an engineer, plain-language explanations of terms if I'm a newcomer. No jargon dumps.
- I decide, you implement. Be upfront about limitations and risks — don't only report the good news.
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.
- 7d ago First seen · 38 lines · 485 tokens per session scan A 4c2fdb1f0613
vibe-coding-playbook CLAUDE.md is an instructions file published in the GitHub repository ayi-ai/vibe-coding-playbook (1 stars, last pushed 3mo ago), licensed MIT. It adds 485 tokens to every session, about $0.0024 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-31.
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).
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).
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.