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.
git clone --depth 1 https://github.com/MatthewSherlin/mushroomdbWrote 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/rules/matthewsherlin/mushroomdb/cursor-rules)<a href="https://agentmods.dev/rules/matthewsherlin/mushroomdb/cursor-rules"><img src="https://agentmods.dev/badge/rules/matthewsherlin/mushroomdb/cursor-rules.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.01470 | $0.01470 |
| Opus 5 | $0.00735 | $0.00735 |
| Sonnet 5 | $0.00294 | $0.00294 |
| Haiku 4.5 | $0.00147 | $0.00147 |
Grade A, and why
cursor-rules 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 88 lines · 1,470 tokens per session scan A c28697614bb9
cursor-rules is a cursor rule published in the GitHub repository MatthewSherlin/mushroomdb (4 stars, last pushed 2d ago), with no licence file. It adds 1,470 tokens to every session, about $0.0073 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-09-05.
Other cursor rules, from other repositories
04-spatial-parser
Guidelines for Spatial RAG and Markdown parsing.
context-loader
Use when starting a new substantive conversation or switching contexts — load relevant memories to prime the session with continuity.
session-memory
Use at conversation wrap-up or when the user explicitly indicates end-of-session — capture residual lessons not captured in-flight.
memory-informed-refactor
Use before substantive refactors — load relevant prior context, capture refactor insights as they land.
jarvis-agent-rules
MCP server jarvis: notes, Jira, knowledge graph, sessions, preferences.
memory-rules.mdc
Cursor rule "memory-rules.mdc" from devviniuchita/memory-system, covering 🧠 neural memory system, 🚀 execution patterns, pattern: problem decomposition, pattern: continuous delivery and 🔄 self-improvement loop.