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/airaalfredsf/project-brain-mcp/cursorrulesgit clone --depth 1 https://github.com/AiraAlfredSF/project-brain-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/rules/airaalfredsf/project-brain-mcp/cursorrules)<a href="https://agentmods.dev/rules/airaalfredsf/project-brain-mcp/cursorrules"><img src="https://agentmods.dev/badge/rules/airaalfredsf/project-brain-mcp/cursorrules.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.00880 | $0.00880 |
| Opus 5 | $0.00440 | $0.00440 |
| Sonnet 5 | $0.00176 | $0.00176 |
| Haiku 4.5 | $0.00088 | $0.00088 |
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 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
code-brain-mcp — Checklist
This project runs the code-brain MCP server, giving you persistent decision
memory, a codebase dependency graph, plan validation, and a self-bootstrapping
constraints file. Work through this checklist as you go.
Session lifecycle
- Call
start_session()at the start of every session. Resets compliance tracking and (on the first call of the process) prints theBRAIN DSL v1schema header needed to interpret every other tool's output. - Periodically call
get_session_health()(roughly every 10 turns). If it returnsSESSION: warningsorSESSION: violations, follow theaction:line(s) before continuing. - Do not call
record_tool_callyourself — the server invokes it automatically after every tool call.
Decision memory (Spec 01)
- Before starting any task, call
get_context(topic)for the task's topic. - Call
list_constraints()to review architectural and technology constraints before making changes that might touch them. - After making an architectural decision (library, pattern, data model,
API shape, etc.), call
log_decision(decision, rationale, alternatives_rejected, tags). - When an approach fails, call
log_failure(description, cause, approach_tried)before trying an alternative.
Codebase graph (Spec 02)
- After first setup, or whenever the code graph seems stale, call
index_codebase()to (re)build the dependency graph. - Before modifying a module, call
get_dependents(module)to see what depends on it. - Before changing a module, call
get_dependencies(module)to understand what it relies on. - Before a significant or risky change, call
get_blast_radius(module)for the full transitive impact. - After pulling new commits, call
diff_graph(since_commit)to see structural changes since the last index. - When starting a task described at a high level, call
find_entry_points(intent)to locate the relevant module(s).
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 First seen · 81 lines · 880 tokens per session scan A 7b6ed8b1d619
cursorrules is a cursor rule published in the GitHub repository AiraAlfredSF/project-brain-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 880 tokens to every session, about $0.0044 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
mempalace-recall-always
Always-on MemPalace recall — search the palace before answering about past work, people, projects, or prior decisions.
dreamd-recall
Recall lessons, decisions, and prior context from the .agent/ memory daemon. Use when starting work in a project that has a .agent/ folder, when the user references a past decision, or when you are about to make a choice that has a documented prior.
session-memory
Use at conversation wrap-up or when the user explicitly indicates end-of-session — capture residual lessons not captured in-flight.
common_memory_bank
I am Cursor, an expert software engineer with a unique characteristic: my memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read…
memsprout
Cursor rule "memsprout" from memsprout/agents, covering using memsprout, search first, capturing, spaces and topics and files.
self-improving-obsidian-llm-wiki
LLM Wiki OS operating rules.