Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/sovantica/engrava-mcp/agents-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/agents-md)<a href="https://agentmods.dev/instructions/sovantica/engrava-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/sovantica/engrava-mcp/agents-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.00770 | $0.00770 |
| Opus 5 | $0.00385 | $0.00385 |
| Sonnet 5 | $0.00154 | $0.00154 |
| Haiku 4.5 | $0.00077 | $0.00077 |
Grade A, and why
engrava-mcp AGENTS.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 5d 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.
This is a copy
92% identical to engrava AGENTS.md — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — engrava-mcp
Canonical guidance for AI coding agents (Claude Code, GitHub Copilot, Cursor, Aider, Continue, OpenAI Codex CLI, and others) working in this repository.
Repository context
This is a public repository (engrava-mcp) — Model Context Protocol server exposing Engrava as agent memory. License: MIT. Primary language: python 3.11+.
Assume every commit message, PR title, PR body, branch name, code comment, and docstring is world-visible. Public-safe by default.
Required reading before generating commits
CLAUDE.md— full context for this repo (quality bar, testing conventions, commit format, branching).CONTRIBUTING.md— contribution flow..github/copilot-instructions.md— architecture, naming patterns, scope reference.BRANCHING.md— branch naming + flow.
Commit hygiene
- Conventional Commits 1.0.0 —
<type>(<scope>): <description>. Types inCLAUDE.md. - Public release tags (
vX.Y.Z) and this repo's GitHub issue/PR numbers (#N) are your durable identifiers. - Locally-documented ADRs (
docs/adr/ADR-NNN-*.md) may be referenced once the file exists in this repo. - Generic feature descriptions and Conventional Commit headers are always welcome.
A pre-commit hook is provided locally to give you a fast feedback loop on commit-message hygiene. Run git commit and you'll see the check fire on any message that wouldn't be appropriate for a public open-source project.
Branch hygiene
Branch names: <type>/<kebab-description>. Plain English. No internal identifiers. ≤ 50 chars.
Examples:
feature/priority-signal-hybrid-searchfix/empty-count-on-mindqldocs/quickstart-update
Self-check before every commit
Before finalising a commit message, ask:
- Could this message, branch name, or referenced symbol reveal information about a workflow that should stay private?
- Am I using only durable public identifiers (release tags, this repo's issue/PR numbers, locally-documented ADRs)?
- Is the message format Conventional Commits?
- Is the branch name plain English in
<type>/<kebab-description>form?
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.
- 5d ago First seen · 60 lines · 770 tokens per session scan A ecd8fda012b2
engrava-mcp AGENTS.md is an instructions file published in the GitHub repository sovantica/engrava-mcp (1 stars, last pushed 5d ago), licensed MIT. It adds 770 tokens to every session, about $0.0038 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to engrava AGENTS.md, differing in 9 lines, and is treated as a copy.
Other instructions, from other repositories
xbrain CLAUDE.md
Claude Code instructions for mrboups/xbrain, covering claude.md, project status, workflow: gsd is the build system, constraints carried over from kickoff and commands.
plur CLAUDE.md
Claude Code instructions for plur-ai/plur, covering claude.md, what is plur, development, package dependency and version bumps.
honcho CLAUDE.md
Claude Code instructions for plastic-labs/honcho, covering claude.md, honcho overview, what is honcho?, core concepts and peer paradigm.
trello-mcp AGENTS.md
AGENTS.md instructions for enthouan/trello-mcp, covering agents.md, project summary, hard constraints, runtime and package manager and common commands.
titen CLAUDE.md
Instructions for RamaAditya49/titen, covering claude.md, read agents.md first, commands, two runtimes, one core and publishing to npm.
hop CLAUDE.md
Instructions for danmartuszewski/hop: Use conventional commit format with imperative mood.