Borrowing it
Nothing to install: this file belongs to sovantica/engrava-mcp. 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/sovantica/engrava-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/sovantica/engrava-mcpWrote 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/sovantica/engrava-mcp/claude-md)<a href="https://agentmods.dev/instructions/sovantica/engrava-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/sovantica/engrava-mcp/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.01959 | $0.01959 |
| Opus 5 | $0.00979 | $0.00979 |
| Sonnet 5 | $0.00392 | $0.00392 |
| Haiku 4.5 | $0.00196 | $0.00196 |
Grade A, and why
engrava-mcp 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — engrava-mcp
This is a public repository (engrava-mcp) — Model Context Protocol server exposing Engrava as agent memory.
Assume every commit message, PR title, PR body, branch name, code comment, and docstring is world-visible. Public-safe by default.
Context
| Aspect | Value |
|---|---|
| License | MIT |
| Primary language | python 3.11+ |
| Default branch for PRs | the active release/vX.Y.Z branch |
| Release flow | Manual version in pyproject.toml / server.json + maintainer-created vX.Y.Z tag on main |
| Contribution model | issues + PRs on GitHub |
Repository-specific rules
- Thin MCP server: consume Engrava's public API only — no internals access.
- Transport: stdio; the surface is MCP tools / resources / prompts.
- Store resolution via env vars (ENGRAVA_MCP_CONFIG, ENGRAVA_DB_PATH, ENGRAVA_MCP_READ_ONLY).
- Quality gate: ruff ALL + mypy strict + 90% test coverage.
Code quality — zero-compromise bar
This is production code maintained to a high quality bar. A feature is not "done" until every point below holds:
- Linting —
ruff checkclean,ruff format --checkclean, no rule disables without a justifying comment. - Typing —
mypy --strictclean. No bareAny. No# type: ignorewithout a justifying inline comment. - Coverage — 90% minimum, enforced by
--cov-fail-under=90. TDD preferred; tests are first-class code. - Docstrings — Google-style on every public symbol (params, returns, raises, examples).
- Domain modelling — concrete types per concept, no catch-all dicts, no god objects.
- Errors — typed exceptions; never bare
except; never swallow errors silently. - No shortcuts — no
TODO/FIXME/HACKin production code; open an issue instead. No dead code. No magic strings. - Secrets — never hard-code API keys; use env vars or config objects; never log secrets.
Run locally before opening a PR
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 · 131 lines · 1,959 tokens per session scan A 943d51e01dca
engrava-mcp CLAUDE.md is an instructions file published in the GitHub repository sovantica/engrava-mcp (1 stars, last pushed today), licensed MIT. It adds 1,959 tokens to every session, about $0.0098 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.