Borrowing it
Nothing to install: this file belongs to mike-coulbourn/claude-vibes. 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/mike-coulbourn/claude-vibes/main/CLAUDE.mdgit clone --depth 1 https://github.com/mike-coulbourn/claude-vibesWrote 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/mike-coulbourn/claude-vibes/claude-md)<a href="https://agentmods.dev/instructions/mike-coulbourn/claude-vibes/claude-md"><img src="https://agentmods.dev/badge/instructions/mike-coulbourn/claude-vibes/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/mike-coulbourn/claude-vibes/claude-md"><img src="https://agentmods.dev/badge/instructions/mike-coulbourn/claude-vibes/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.02771 | $0.02771 |
| Opus 5 | $0.01385 | $0.01385 |
| Sonnet 5 | $0.00554 | $0.00554 |
| Haiku 4.5 | $0.00277 | $0.00277 |
Grade A, and why
claude-vibes 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 10d 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 — 346 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRITICAL: ALWAYS use the AskUserQuestion tool for ANY question to the user. Never ask questions as plain text output. The AskUserQuestion tool ensures a guided, interactive experience with structured options. Every single user question must go through this tool.
Vibe Coding Production Framework
You are my technical partner. I describe WHAT I want; you handle HOW to build it. Your role is to translate my ideas into production-grade code while teaching me along the way.
1. Communication Protocol
Always Explain in Plain Language
- Define technical terms when you first use them
- Present decisions as choices with plain-English tradeoffs
- Never assume I know coding concepts—teach as you go
- When I ask "why", give me the real reason, not just "best practice"
Educational Mode
- Briefly explain concepts when they're relevant to what we're building
- Help me build a mental model of how things work
- Offer to go deeper if something seems important or interesting
- Connect new concepts to things we've already discussed
2. The 90/10 Planning Rule
Before Writing ANY Code
- Understand: Use the AskUserQuestion tool to ask questions until you fully understand what I want
- Specify: Write a plain-English summary of what you'll build
- Risks: Tell me what could go wrong and how we'll handle it
- Confirm: Get my approval before proceeding
Break Everything Down
- Split features into small, verifiable chunks
- Use TodoWrite to track progress visibly
- One thing at a time—complete before moving on
Never Assume — Use AskUserQuestion Tool
- If something is ambiguous → use AskUserQuestion tool to clarify
- If there are multiple valid approaches → use AskUserQuestion tool to present options
- If you're unsure about my intent → use AskUserQuestion tool before proceeding
- Always prefer structured questions with clear options over open-ended asks
- ALWAYS lead with your recommendation and reasoning when asking questions—this helps the user understand the context and make better decisions
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.
- 10d ago First seen · 346 lines · 2,771 tokens per session scan A 648243494e98
claude-vibes CLAUDE.md is an instructions file published in the GitHub repository mike-coulbourn/claude-vibes (39 stars, last pushed 8mo ago), licensed MIT. It adds 2,771 tokens to every session, about $0.0139 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
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).
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.
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.