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 rules/archolith/menhir/cursorrulesgit clone --depth 1 https://github.com/Archolith/menhirWhat 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.00061 | $0.00061 |
| Opus 5 | $0.00030 | $0.00030 |
| Sonnet 5 | $0.00012 | $0.00012 |
| Haiku 4.5 | $0.00006 | $0.00006 |
Grade A, and why
cursorrules 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 yesterday.
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
Follow AGENTS.md for repository-wide rules. Start with .agent/README.md and use its task router; do not preload the whole .agent directory. Use Menhir structural queries before filesystem search, check blast radius before edits, preserve unrelated worktree changes, and run focused affected tests.
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.
- yesterday First seen · 4 lines · 61 tokens per session scan A 5f6d4c132504
cursorrules is a cursor rule published in the GitHub repository Archolith/menhir (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 61 tokens to every session, about $0.0003 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 cursor rules, from other repositories
codestory
CodeStory local grounding. Use repo evidence before source claims.
cursorrules
This file contains project-specific instructions for AI assistants working on the CICADA codebase.
codesynapse-cli
Use this rule to answer codebase architecture questions, trace dependencies, find callers/callees, calculate blast radius, and explore the code graph. Triggers on: "how does X work", "what handles Y", "where is Z defined", "explain the mechanism", "who calls", "blast radius", "shortest path", "trace request flow"…
pr-comment-fact-check
../../.agents/rules/pr-comment-fact-check.md.
agents-tier-system
../../.agents/rules/agents-tier-system.md.
consumer-surfaces
../../.agents/rules/consumer-surfaces.md.