Borrowing it
Nothing to install: this file belongs to funtusov/mcp-server-architect. 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/funtusov/mcp-server-architect/main/CLAUDE.mdgit clone --depth 1 https://github.com/funtusov/mcp-server-architectWrote 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/funtusov/mcp-server-architect/claude-md)<a href="https://agentmods.dev/instructions/funtusov/mcp-server-architect/claude-md"><img src="https://agentmods.dev/badge/instructions/funtusov/mcp-server-architect/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.00848 | $0.00848 |
| Opus 5 | $0.00424 | $0.00424 |
| Sonnet 5 | $0.00170 | $0.00170 |
| Haiku 4.5 | $0.00085 | $0.00085 |
Grade A, and why
mcp-server-architect 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Guidelines for architect-mcp
Commands
- Setup:
uv add -e .(install in dev mode) - Dependencies:
uv add google-genai python-dotenv(required packages) - Build:
uv build --no-sources - Run:
uvx mcp-server-architect - Lint:
ruff check . - Format:
ruff format . - Fix lint issues:
ruff check --fix .
Publishing a New Version
For a complete guide on building, testing, and publishing new versions, see PUBLISH.md for detailed step-by-step instructions.
Testing
- Run the pytest integration tests when developing and before publishing
- For normal development, use linting to check code quality:
ruff check .
Integration Tests Best Practices
- Use pytest-recording for integration tests to record live API responses
- Never use mocks in integration tests; they create brittle tests that don't catch real issues
- Run tests with recorded cassettes:
uv run pytest tests/ -v - To rewrite all cassettes:
uv run pytest tests/ --record-mode=all - Remember to check cassettes into source control but filter sensitive data
Committing Changes
When committing changes:
- Use a succinct one-line commit message
- Don't include "Generated with Claude Code" or "Co-Authored-By" lines
- Run linter checks before committing
- Always add all modified files including lock files for a clean state (
git add .) - If certain files should not be committed, explicitly gitignore them
UV Cheatsheet
- Add dependency:
uv add <package>oruv add <package> --dev - Remove dependency:
uv remove <package>oruv remove <package> --dev - Run in venv:
uv run <command>(e.g.uv run pytest) - Sync environment:
uv sync - Update lockfile:
uv lock - Install tool:
uv tool install <tool>(e.g.uv tool install ruff)
Code Style
- Line length: 120 characters (configured in pyproject.toml)
- Python 3.10+ compatible
- Document functions with docstrings (triple quotes)
- File structure: shebang line, docstring, imports, constants, classes/functions
- Imports: standard library first, then third-party, then local modules
- Error handling: use try/except blocks with specific exceptions and logging
- Naming: snake_case for variables/functions, PascalCase for classes
- Logging: use the module-level logger defined at the top of each file
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 · 83 lines · 848 tokens per session scan A 28f3ba26cb30
mcp-server-architect CLAUDE.md is an instructions file published in the GitHub repository funtusov/mcp-server-architect (4 stars, last pushed 1y ago), licensed MIT. It adds 848 tokens to every session, about $0.0042 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.