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/savagelysubtle/big-brain-memory-bank/000-xml-cursor-rulesgit clone --depth 1 https://github.com/savagelysubtle/BIG-BRAIN-Memory-BankWrote 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/savagelysubtle/big-brain-memory-bank/000-xml-cursor-rules)<a href="https://agentmods.dev/rules/savagelysubtle/big-brain-memory-bank/000-xml-cursor-rules"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/000-xml-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.00000 | $0.02060 |
| Opus 5 | $0.00000 | $0.01030 |
| Sonnet 5 | $0.00000 | $0.00412 |
| Haiku 4.5 | $0.00000 | $0.00206 |
Grade A, and why
000-xml-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 6d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<naming-convention>
<pattern>PREFIX-name.mdc</pattern>
<prefixes>
<prefix code="0XX">Core standards (highest priority)</prefix>
<prefix code="1XX">Tool configs</prefix>
<prefix code="3XX">Testing standards</prefix>
<prefix code="4XX">Documentation standards</prefix>
<prefix code="1XXX">Language rules</prefix>
<prefix code="2XXX">Framework rules</prefix>
<prefix code="8XX">Workflows</prefix>
<prefix code="9XX">Templates</prefix>
<prefix code="__XXX_name.mdc">Private rules</prefix>
</prefixes>
</naming-convention>
<glob-patterns>
<pattern type="core-standards">.cursor/rules/*.mdc</pattern>
<pattern type="language-rules">src/**/*.{js,ts}</pattern>
<pattern type="testing-standards">**/*.test.{js,ts}</pattern>
<pattern type="react-components">src/components/**/*.tsx</pattern>
<pattern type="documentation">docs/**/*.md</pattern>
<pattern type="configuration">*.config.{js,json}</pattern>
<pattern type="build-artifacts">dist/**/*</pattern>
<pattern type="multiple-extensions">src/**/*.{js,jsx,ts,tsx}</pattern>
<pattern type="multiple-files">dist/**/*, docs/**/*.md</pattern>
</glob-patterns>
<description-field>
<format>Use deterministic ACTION TRIGGER OUTCOME format</format>
<pattern>WHEN X occurs THEN do Y (e.g., "WHEN writing Python code ALWAYS use type hints")</pattern>
<length>Keep under 120 characters while maintaining clear intent</length>
</description-field>
<globs-field>
<format>Standard glob patterns without quotes</format>
<examples>
<example>*.js</example>
<example>src/**/*.py</example>
<example>**/*.{ts,tsx}</example>
</examples>
</globs-field>
<trigger-sections>
<section name="activation">
<purpose>Define clear trigger conditions and responses</purpose>
<example>
<activation>
<trigger>Memory bank update</trigger>
<action>Review all memory bank files</action>
</activation>
</example>
</section>
</trigger-sections>
<procedural-sections>
<section name="steps" or "process" or "workflow">
<purpose>Define ordered sequences of actions</purpose>
<example>
<process>
<step>Review requirements</step>
<step>Analyze existing code</step>
<step>Create implementation plan</step>
</process>
</example>
</section>
</procedural-sections>
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.
- 6d ago First seen · 192 lines · 0 tokens per session scan A fc9e8d4ba9b2
000-xml-cursor-rules is a cursor rule published in the GitHub repository savagelysubtle/BIG-BRAIN-Memory-Bank (5 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,060 tokens. 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
composer-coding-excellence
Coding craft — surgical edits, convention matching, no scope creep, no slop comments, no fabricated APIs.
composer-core
Always-on builder spine — continue the app, demoable slice, Build loop, Run/Wired handoff, ask only on high confusion weight.
composer-reasoning
High-stakes judgment for architectural or multi-option work — tradeoffs, one-way doors, reason-then-re-evaluate, honest pushback.
clarify-first
Infer-and-act by default — ask only on high confusion weight, after inspecting, with a decision-linked question.
composer-debugging
Root-cause debugging — reproduce, trace data flow, test cheapest hypothesis, fix the cause not the symptom.
composer-deep-research
Edge-case research for audits, vendor comparisons, and unfamiliar APIs — primaries first, iterative retrieval, explicit conflicts; not the default build path.