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/brainos-hq/brain-os/cursor-brain-osgit clone --depth 1 https://github.com/brainOS-HQ/brain-osWrote 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/brainos-hq/brain-os/cursor-brain-os)<a href="https://agentmods.dev/rules/brainos-hq/brain-os/cursor-brain-os"><img src="https://agentmods.dev/badge/rules/brainos-hq/brain-os/cursor-brain-os.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.00414 | $0.00414 |
| Opus 5 | $0.00207 | $0.00207 |
| Sonnet 5 | $0.00083 | $0.00083 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
cursor-brain-os 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
Brain OS rules for Cursor
This project uses Brain OS for persistent operational state across AI agents. State lives in .brain/.
Canonical instructions
See AGENTS.md at the project root. It is the cross-tool source of truth. This .mdc file exists only so Cursor picks up the same rules.
Critical rules (also in AGENTS.md)
-
Brain OS MCP tools are the primary data source for any project-state question. The tools are exposed as
brain-osin your MCP server list. Do NOT grep source code to answer "what should I focus on" — callmcp__brain-os__focus_get. -
Routing order:
entity_read→plan_read→focus_get→semantic_recall→decision_check→pattern_detect. Mutating tools (decision_log,entity_update,plan_*,decision_refresh) require a priordecision_checkcall. -
Conflict handling: if
decision_checkreturnsconflict, do not proceed without explicit user confirmation. Ifcaution, surface the relevant active decision and ask. -
Output format: fixed-column tables for
focus_get, single-card format forentity_read. No long-form rephrasing of JSON. -
Command vocabulary: the user may type bare keywords (
brain,focus,decide,wrap,retro,patterns,graph,strategy) with or without a leading/. Run the matching MCP tool sequence — do not search the repo for these words. -
No todo lists for state-reading questions. Call the tool, return the answer.
-
Drift check: if your first action on a state question is reading
.brain/files directly, stop and re-route through the MCP tools.
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 · 30 lines · 414 tokens per session scan A 02724dd8b033
cursor-brain-os is a cursor rule published in the GitHub repository brainOS-HQ/brain-os (6 stars, last pushed 11d ago), licensed MIT. It adds 414 tokens to every session, about $0.0021 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
cursorrules
Zettelkasten memory for AI agents. Markdown cards in /.memex/cards/ with [[wikilinks]]. npm package @touchskyer/memex. Distributed as CLI + MCP server + Claude Code plugin + VS Code extension + Pi extension.
lians-memory
Current Lians task, control policy, and bounded context.
ctxfile
You have access to the ctxfile MCP tools (getcontext, savesession, continuethread, listthreads, ingestcontext). These behaviors make context capture automatic. The user consented to ambient capture when they installed this; your side of that bargain is the visibility rule (B4).
avos-agent-workflow
Avos memory workflow for AI coding agents. Guides codebase search and history lookup.
obsidian-hub-spoke-graph
Hub-and-spoke (MOC) linking for Obsidian vault notes — no peer mesh, leaves up-link only.
vault-safety
Safety rules when writing to an Obsidian vault through Obsidian Bridge.