Borrowing it
Nothing to install: this file belongs to meob/mcp-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/meob/mcp-blueprint/main/CLAUDE.mdgit clone --depth 1 https://github.com/meob/mcp-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/meob/mcp-blueprint/claude-md)<a href="https://agentmods.dev/instructions/meob/mcp-blueprint/claude-md"><img src="https://agentmods.dev/badge/instructions/meob/mcp-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/meob/mcp-blueprint/claude-md"><img src="https://agentmods.dev/badge/instructions/meob/mcp-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.00578 | $0.00578 |
| Opus 5 | $0.00289 | $0.00289 |
| Sonnet 5 | $0.00116 | $0.00116 |
| Haiku 4.5 | $0.00058 | $0.00058 |
Grade A, and why
mcp-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 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.
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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This document defines the general development guidelines for AI coding assistants contributing to this repository.
These guidelines are intentionally project-independent and should remain applicable across different projects.
Project-specific requirements are documented in the repository documentation.
General Principles
Produce software that is:
- Correct
- Readable
- Maintainable
- Modular
- Production-ready
Always prefer simplicity over unnecessary complexity.
Choose solutions that minimize long-term maintenance.
Read the Documentation First
Before making significant changes, read the Markdown documentation available in the project root.
The project documentation defines:
- goals
- architecture
- implementation priorities
- design decisions
Follow the documented architecture unless explicitly instructed otherwise.
Language
Use English consistently for:
- source code
- comments
- docstrings
- documentation
- commit messages
- prompts
- examples
- configuration descriptions
- error messages
Do not mix languages.
Code Quality
Write clean, explicit and readable code.
Prefer:
- small functions
- focused classes
- modular components
- reusable code
Avoid:
- duplicated logic
- unnecessary abstractions
- premature optimization
- hidden side effects
Prefer composition over inheritance whenever practical.
Dependencies
Keep dependencies to a minimum.
Before introducing a new library, verify that it provides significant value.
Avoid overlapping libraries that solve the same problem.
Configuration
Avoid hardcoded values.
Use configuration files or environment variables whenever appropriate.
Testing
Whenever practical, accompany new functionality with automated tests.
Code without tests should be considered incomplete.
Documentation
Documentation is part of the implementation.
Whenever functionality or architecture changes, update the relevant documentation.
Git
Use Git from the beginning.
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 · 178 lines · 578 tokens per session scan A 3e90754c36d6
mcp-blueprint CLAUDE.md is an instructions file published in the GitHub repository meob/mcp-blueprint (0 stars, last pushed 14d ago), licensed Apache-2.0. It adds 578 tokens to every session, about $0.0029 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).
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.
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.