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/archolith/menhir/claude-mdgit clone --depth 1 https://github.com/Archolith/menhirWrote 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/archolith/menhir/claude-md)<a href="https://agentmods.dev/instructions/archolith/menhir/claude-md"><img src="https://agentmods.dev/badge/instructions/archolith/menhir/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 | $0.00092 | $0.00092 |
| Opus 5 | $0.00046 | $0.00046 |
| Sonnet 5 | $0.00018 | $0.00018 |
| Haiku 4.5 | $0.00009 | $0.00009 |
Grade A, and why
menhir 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 4d 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.
What it actually says
Menhir
Follow AGENTS.md. Start with .agent/README.md and use its task router;
do not read the entire .agent/ tree by default.
Maintainer MCP sync: the maintainer workspace generates Menhir's MCP client entries from a central registry. If the entry point, args, environment, or cwd changes, update and regenerate that registry.
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.
- 4d ago First seen · 8 lines · 92 tokens per session scan A 0060b5433459
menhir CLAUDE.md is an instructions file published in the GitHub repository Archolith/menhir (2 stars, last pushed today), licensed Apache-2.0. It adds 92 tokens to every session, about $0.0005 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
remembrallmcp CLAUDE.md
Claude Code instructions for roboticforce/remembrallmcp, covering remembrallmcp, quick reference, build & run, start database and build everything.
remembrallmcp AGENTS.md
AGENTS.md instructions for roboticforce/remembrallmcp, covering remembrallmcp, scope, project overview, common commands and cli reference.
repobrain copilot-instructions.md
Copilot instructions for study8677/repobrain, covering github copilot bootstrap instructions and hard rule — query the repobrain hub first.
trace-mcp CLAUDE.md
Claude Code instructions for nikolai-vysotskyi/trace-mcp, covering trace-mcp development guide, what this project is, agent behavior — read before every task, no flattery, no filler and disagree when the premise is wrong.
supi CLAUDE.md
Claude Code instructions for mrclrchtr/supi, covering claude.md, development status, pi docs-first rule, documentation expectations and package layout convention.
trace-mcp AGENTS.md
AGENTS.md instructions for nikolai-vysotskyi/trace-mcp: IMPORTANT: For ANY code exploration task, ALWAYS use trace tools first. NEVER use Read/Grep/Glob/Bash(ls,find) for navigating source code.