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/maingit 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/main)<a href="https://agentmods.dev/rules/savagelysubtle/big-brain-memory-bank/main"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/main.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.00000 | $0.00963 |
| Opus 5 | $0.00000 | $0.00481 |
| Sonnet 5 | $0.00000 | $0.00193 |
| Haiku 4.5 | $0.00000 | $0.00096 |
Grade A, and why
main 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.
How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: BIG BRAIN Memory Bank System Core Rules globs: ["**/*"] alwaysApply: true
BIG BRAIN Memory Bank System
The Memory Bank is the core of BIG BRAIN's capability for maintaining context between sessions despite complete memory resets.
2.0.0
System Overview
The BIG BRAIN Memory Bank system provides a hierarchical, modular architecture for maintaining perfect memory between sessions. The system is designed around a cognitive memory model with specialized components for different types of knowledge and processing requirements.
Core Architecture
The Memory Bank implements a layered architecture:
-
Foundation Layer - Core system infrastructure and protocols
- Enhanced Complexity Framework (Level 1-4)
- Reference Verification System
- Task Escalation Protocol
- Section Checkpoint System
- Creative Phase Metrics
- BIG Command Protocol
-
Memory Layer - Specialized memory structures
- Core memory files (projectbrief.md, activeContext.md, etc.)
- Long-term memory repositories
- Session-based working memory
- Procedural memory patterns
-
Workflow Layer - Process patterns for effective operation
- Plan mode workflows
- Act mode workflows
- Hybrid workflows
- Bedtime protocol
-
Interface Layer - Interaction patterns and commands
- Command protocols
- Status indicators
- Memory update triggers
- Context switches
Integrated Components
The system provides these integrated capabilities:
- Adaptive Complexity - Task-appropriate rigor scaling
- Reference Verification - Memory integrity validation
- Section Checkpoints - Progress tracking and verification
- Task Escalation - Dynamic complexity adaptation
- Creative Phases - Structured exploration framework
- Command Protocols - Unified interaction model
- Verification Framework - Multi-level quality assurance
Memory Bank Structure
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 · 144 lines · 0 tokens per session scan A 8d45b7d9b86c
main 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 963 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
wrapup
End-of-session wrap-up: summarizes the session and pushes a log to the project's linked NotebookLM notebook. Activate with @wrapup in chat, or "wrap up", "save this session", or "end of session".
memory-bank
You are an expert software engineer with a unique characteristic: your memory resets completely between sessions. This isn't a limitation - it's what drives you to maintain perfect documentation. At the beginning of each dialogue, you rely ENTIRELY on your Memory Bank to understand the project and continue work…
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.
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.