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/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/500-rule-organization-enforcer)<a href="https://agentmods.dev/rules/savagelysubtle/big-brain-memory-bank/500-rule-organization-enforcer"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/500-rule-organization-enforcer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/savagelysubtle/big-brain-memory-bank/500-rule-organization-enforcer"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/500-rule-organization-enforcer.svg" alt="Reviewed on agentmods" width="80" 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.02647 | $0.02647 |
| Opus 5 | $0.01324 | $0.01324 |
| Sonnet 5 | $0.00529 | $0.00529 |
| Haiku 4.5 | $0.00265 | $0.00265 |
Grade A, and why
500-rule-organization-enforcer 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 12d 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 — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TL;DR: The Rule Organization Enforcer ensures all rule files are placed in their correct locations according to the established directory structure, maintaining system integrity and discoverability.
1.0.0
```
.cursor/rules/
├── BIG_BRAIN/ # All BIG BRAIN specific rules
│ ├── Core/ # Core BIG BRAIN functionality
│ │ ├── Foundation/ # Foundation layer components (Phase 1)
│ │ ├── Verification/ # Verification framework components (Phase 2)
│ │ ├── Command/ # Command protocol components (Phase 3)
│ │ ├── Creative/ # Creative phase components (Phase 4)
│ │ ├── Checkpoint/ # Checkpoint system components (Phase 5)
│ │ └── Escalation/ # Task escalation components (Phase 6)
│ ├── Identity/ # BIG BRAIN identity definition
│ ├── Protocols/ # Protocol-specific rules
│ └── Utilities/ # BIG BRAIN utility functions
├── Codebase/ # All codebase-related rules
│ ├── Languages/ # Language-specific rules
│ ├── Frameworks/ # Framework-specific rules
│ └── Patterns/ # Code pattern rules
└── main.mdc # Main rule file
```
Each rule file must be placed in the appropriate directory based on its function and purpose.
1. **Core Foundation Layer (040-090)**
- Format: `0XX-descriptive-name.mdc`
- Location: `.cursor/rules/BIG_BRAIN/Core/Foundation/`
- Examples: `040-enhanced-complexity-framework.mdc`
2. **Core Verification Framework (100-130)**
- Format: `1XX-descriptive-name.mdc`
- Location: `.cursor/rules/BIG_BRAIN/Core/Verification/`
- Examples: `100-memory-file-verification.mdc`
3. **Core Command Protocol (140-170)**
- Format: `1XX-descriptive-name.mdc`
- Location: `.cursor/rules/BIG_BRAIN/Core/Command/`
- Examples: `140-unified-command-interface.mdc`
4. **Core Creative Phase (180-210)**
- Format: `1XX-descriptive-name.mdc` or `2XX-descriptive-name.mdc`
- Location: `.cursor/rules/BIG_BRAIN/Core/Creative/`
- Examples: `180-creative-process-structure.mdc`
5. **Core Checkpoint System (220-250)**
- Format: `2XX-descriptive-name.mdc`
- Location: `.cursor/rules/BIG_BRAIN/Core/Checkpoint/`
- Examples: `220-checkpoint-definition.mdc`
6. **Core Task Escalation (260-290)**
- Format: `2XX-descriptive-name.mdc`
- Location: `.cursor/rules/BIG_BRAIN/Core/Escalation/`
- Examples: `260-escalation-triggers.mdc`
7. **BIG BRAIN Identity**
- Format: `000-descriptive-name.mdc`
- Location: `.cursor/rules/BIG_BRAIN/Identity/`
- Examples: `000-big-brain-identity.mdc`
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.
- 12d ago First seen · 295 lines · 2,647 tokens per session scan A e11a804f79bc
500-rule-organization-enforcer is a cursor rule published in the GitHub repository savagelysubtle/BIG-BRAIN-Memory-Bank (5 stars, last pushed 1y ago), licensed MIT. It adds 2,647 tokens to every session, about $0.0132 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
web
Web build conventions (separate from native and RN JS).
components
Component patterns and UI conventions.
git
Git workflow and commit conventions.
verification-before-completion
Require fresh, scope-appropriate evidence before any completion claim. Distinguishes implemented, locally verified, repository-green, PR-green, deployed, and observed-stable states.
_project
Project-wide conventions and developer environment context (RN monorepo, no-Mac dev).
full-stack-ship-discipline
Require frontend changes and their DB/RPC/RLS/storage/secret dependencies to ship and be remotely verified together. Apply when implementing code that reads or writes backend state. Do not apply to plan- or present-then-stop audits; production data mutation still requires confirmation.