Borrowing it
Nothing to install: this file belongs to Archolith/menhir. 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/Archolith/menhir/main/AGENTS.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/agents-md)<a href="https://agentmods.dev/instructions/archolith/menhir/agents-md"><img src="https://agentmods.dev/badge/instructions/archolith/menhir/agents-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/archolith/menhir/agents-md"><img src="https://agentmods.dev/badge/instructions/archolith/menhir/agents-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.00718 | $0.00718 |
| Opus 5.5 | $0.00287 | $0.00287 |
| Sonnet 5.5 | $0.00144 | $0.00144 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
menhir 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 3d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Menhir agent instructions
These instructions apply to the entire repository.
Start here
- Read
.agent/README.md. It is a router; do not preload all of.agent/. - Follow the task-specific route it names. Read large architecture, data-model, endpoint, or memory-design references only when the task requires them.
- Before code exploration, confirm Menhir appears in
query_structure(query_type="projects"). Use structural queries before filesystem search, and checkblast_radiusonce per file before editing. - Verify the repository root, current branch, and worktree status. Preserve unrelated changes and stage files explicitly.
Implementation rules
- Python 3.12+, builtin generics, explicit public return types, and small composable modules.
- Keep external LLM, embedding, Neo4j, and auth configuration in environment variables. Never commit or record secrets.
- Extend the canonical backend/runtime and MCP contracts instead of creating parallel paths.
- Treat stale structural anchors and incomplete indexes as inconclusive until current code is checked.
- Use
.agent/workflows/feature_planning.mdbefore a semi-large or cross-cutting change. - Use
.agent/workflows/code_conventions.mdfor code style and.agent/maintenance.mdfor changelog and closeout requirements.
Verification
- Follow
.agent/workflows/run_and_test.md; it is the authoritative risk-based test and reporting policy. - Run the smallest credible tests for the changed behavior on the maintainer machine. Use
query_structure(query_type="affected_tests")as one selection input, then confirm it from callers, contracts, and existing tests because an empty or stale structural mapping is not evidence that no test is needed. Add direct contract/regression tests for every changed deployment boundary and run matching lint/static checks on changed paths.
- Do not run the complete repository suite locally as a routine implementation or deployment step. Push the reviewed commit and let required CI run the complete suite on that exact SHA. Production publication or promotion must remain blocked until all required CI checks for that SHA are green.
- If CI fails, reproduce the failing test plus its affected neighbors locally, fix them, and push the new SHA; do not repeatedly rerun the complete suite on the maintainer machine. A broad local run is exceptional and requires an explicit reason such as changing test collection or shared test infrastructure.
- Live Neo4j/LLM tests require explicit opt-in and the documented environment.
- Report commands actually run and distinguish failures from tests that were not run.
- Stage files explicitly by path; never
git add .orgit add -A. Leave unrelated changes unstaged.
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.
- 3d ago Changed · +3 lines · +45 tokens per session 6d202fc408a1
- 1mo ago Changed · +10 lines · +98 tokens per session c9e92cac9ffa
- 1mo ago Changed · +3 lines · +58 tokens per session bf9695c7ae03
- 1mo ago Changed · +7 lines · +122 tokens per session d48174904204
- 1mo ago First seen · 35 lines · 395 tokens per session scan A 39ca9cbca274
menhir AGENTS.md is an instructions file published in the GitHub repository Archolith/menhir (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 718 tokens to every session, about $0.0029 per session on Opus 5.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
weld copilot-instructions.md
Copilot instructions for configflux/weld: Use @docs/architecture/principles.md for architecture-sensitive changes.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).