Borrowing it
Nothing to install: this file belongs to faizkhairi/claude-code-blueprint. 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/faizkhairi/claude-code-blueprint/main/CLAUDE.mdgit clone --depth 1 https://github.com/faizkhairi/claude-code-blueprintWrote 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/faizkhairi/claude-code-blueprint/claude-md)<a href="https://agentmods.dev/instructions/faizkhairi/claude-code-blueprint/claude-md"><img src="https://agentmods.dev/badge/instructions/faizkhairi/claude-code-blueprint/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.03009 | $0.03009 |
| Opus 5 | $0.01504 | $0.01504 |
| Sonnet 5 | $0.00602 | $0.00602 |
| Haiku 4.5 | $0.00301 | $0.00301 |
Grade A, and why
claude-code-blueprint CLAUDE.md scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| API / server route | curl or fetch the live endpoint, check the response is real data. **Then also run the `Wiring (new symbol)` row**: a route can answer curl while being registered only in a test harness, never in th How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Global Claude Behavior Rules
Verify-After-Complete (MANDATORY)
After finishing any implementation, task, or plan, ALWAYS run a verification step before declaring it done. This is non-negotiable.
Skip-excuse: "the edit obviously landed." Obvious is the feeling, not the check.
What to verify depends on what was built:
| Work Type | Verification Steps |
|---|---|
| Code / feature | Run tests, run type check, run build. Then also run the Wiring (new symbol) row: green tests prove the code works, not that anything reaches it. |
| API / server route | curl or fetch the live endpoint, check the response is real data. Then also run the Wiring (new symbol) row: a route can answer curl while being registered only in a test harness, never in the production router. |
| Deployment | Hit the production URL, confirm it's not the fallback/empty state |
| Config change | Confirm the config was actually picked up (e.g. env vars, settings) |
| Dependency change | Confirm the install succeeded and nothing broke |
| Git operation | git status to confirm clean state; git log to confirm commit is correct |
| File edit | Re-read the file after editing to confirm the change landed correctly |
| Fact/data update | Search for the NEW value (confirm present) AND search for the OLD value (confirm absent everywhere). Stale copies in other locations are the #1 missed verification. |
| Wiring (new symbol) | Always ADDITIONAL to whichever row above matched; never a substitute for it, and never sufficient alone. Verify goal-backward: the symbol EXISTS -> is not a STUB/TODO -> something IMPORTS/REGISTERS/CALLS it -> data FLOWS end-to-end. Zero call sites = dead code: wire it now, or mark it deferred with a tracking item. Same principle as "An agent you never invoke is dead weight", applied to code. |
Verification mindset
- Don't assume it worked: run the check. A passing build does not mean correct behavior.
- Check the actual output, not just exit codes. A 200 response returning
{ weeks: [], totalContributions: 0 }is not the same as a successful response with real data. - When something looks suspiciously perfect (zero errors, empty state "as expected"), investigate whether it's working correctly or silently failing gracefully.
- End-to-end over unit: the most important check is always the final output the user would see, not intermediate steps.
- Bidirectional fact checks: when updating a value (test count, version, date), grep for the OLD value across the entire scope. A fact that appears in 2 places but is only updated in 1 is a silent inconsistency.
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.
- 8d ago First seen · 179 lines · 3,009 tokens per session scan A c6bf452edb13
claude-code-blueprint CLAUDE.md is an instructions file published in the GitHub repository faizkhairi/claude-code-blueprint (70 stars, last pushed 26d ago), licensed MIT. It adds 3,009 tokens to every session, about $0.0150 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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).
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.