Borrowing it
Nothing to install: this file belongs to rtazima/claude-proj-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/rtazima/claude-proj-blueprint/main/CLAUDE.mdgit clone --depth 1 https://github.com/rtazima/claude-proj-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/rtazima/claude-proj-blueprint/claude-md)<a href="https://agentmods.dev/instructions/rtazima/claude-proj-blueprint/claude-md"><img src="https://agentmods.dev/badge/instructions/rtazima/claude-proj-blueprint/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/rtazima/claude-proj-blueprint/claude-md"><img src="https://agentmods.dev/badge/instructions/rtazima/claude-proj-blueprint/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.02616 | $0.02616 |
| Opus 5.5 | $0.01046 | $0.01046 |
| Sonnet 5.5 | $0.00523 | $0.00523 |
| Haiku 4.5 | $0.00262 | $0.00262 |
Grade A, and why
claude-proj-blueprint 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 1mo 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[SPEC] Project Name
Project
[SPEC] Describe the project in 2-3 lines.
See docs/product/vision.md for the full product vision.
Tech Stack
[SPEC] List the actual stack. Example:
- Backend: [language + framework]
- Frontend: [language + framework]
- Database: [database]
- Tests: [test frameworks]
- Package manager: [manager]
Architecture
/src→ production code/docs→ Obsidian vault (PRDs, ADRs, specs, runbooks)/.claude/→ skills, commands, agents, hooks
Documentation directories
/docs/product/→ PRDs, personas, roadmap/docs/architecture/→ ADRs (Architecture Decision Records)/docs/specs/→ modular project specifications/docs/runbooks/→ deploy, debug, onboarding, post-mortems
Code Conventions
[SPEC] Define your team's conventions. Example:
- Style: [linter, formatter, rules]
- Types: [typing policy]
- Commits: Conventional Commits (
feat:,fix:,docs:,refactor:,test:) - Commit body: inclua
Não alterou:listando arquivos/módulos intencionalmente não modificados - Branches:
feature/,fix/,docs/,refactor/ - PRs: always with description, reference PRD/ADR when applicable
Commands
[SPEC] Day-to-day commands. Example:
[dev command]→ dev server[test command]→ tests[lint command]→ lint
Slash commands
/implement <PRD>→ implement feature from PRD (Plan Mode → code → test → docs)/ralph <PRD>→ persistence mode: don't stop until all acceptance criteria pass/debug <error|file>→ systematic debugging: reproduce → isolate → fix → verify/refactor <file|module>→ safe refactoring with tests before and after each step/clean [file|dir]→ remove AI-generated slop from code/debt [dir]→ scan for technical debt, produce prioritized report/learn [--commits N]→ analyze recent work, extract patterns, improve skills/deploy→ run deploy checklist/memory <search|index|stats>→ long-term memory operations/spec-review <path>→ run agent audit (security + compliance + quality + performance)/discover <path>→ legacy code archaeology: populate empty tiered lookup layers before /implement or /refactor
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.
- 1mo ago First seen · 213 lines · 2,616 tokens per session scan A 9025505121e9
claude-proj-blueprint CLAUDE.md is an instructions file published in the GitHub repository rtazima/claude-proj-blueprint (22 stars, last pushed 5mo ago), licensed MIT. It adds 2,616 tokens to every session, about $0.0105 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-30.
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.