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/800-memory-operations-workflow)<a href="https://agentmods.dev/rules/savagelysubtle/big-brain-memory-bank/800-memory-operations-workflow"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/800-memory-operations-workflow.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.03178 | $0.03178 |
| Opus 5 | $0.01589 | $0.01589 |
| Sonnet 5 | $0.00636 | $0.00636 |
| Haiku 4.5 | $0.00318 | $0.00318 |
Grade A, and why
800-memory-operations-workflow 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 — 487 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TL;DR: This rule establishes standardized workflows for memory bank operations, ensuring consistent processes for initialization, updates, verification, and session transitions despite memory resets.
1.0.0
1. **Initialization Workflows**
- Session startup procedures
- Memory bank loading
- Context restoration
- System verification
- Task preparation
2. **Operational Workflows**
- Memory bank updates
- State tracking
- Information retrieval
- Progressive knowledge building
- Context switching
3. **Verification Workflows**
- Integrity checking
- Consistency validation
- Reference verification
- Performance monitoring
- Error detection and recovery
4. **Transition Workflows**
- Session summarization
- State preservation
- Bedtime procedures
- Wakeup sequence
- Continuity maintenance
Each workflow type has specific processes, checks, and documentation requirements.
1. **Memory Bank Loading**
- Retrieve core memory files:
- projectbrief.md
- productContext.md
- activeContext.md
- systemPatterns.md
- techContext.md
- progress.md
- Verify file existence and accessibility
- Load content into working memory
- Note any missing or inaccessible files
2. **Context Assessment**
- Review activeContext.md for current focus
- Identify recent changes and current status
- Note open issues and questions
- Understand overall progress
- Recognize next planned steps
3. **System Verification**
- Check version compatibility
- Verify cross-references
- Validate memory bank structure
- Confirm rule availability
- Identify any integrity issues
4. **Task Contextualization**
- Relate current task to project context
- Position within implementation plan
- Identify relevant components
- Determine complexity level
- Prepare appropriate resources
5. **Readiness Confirmation**
- Verify all required information is available
- Confirm understanding of current state
- Identify any missing context
- Request additional information if needed
- Signal initialization completion
This workflow ensures proper system readiness before task execution.
1. **Change Assessment**
- Identify what information has changed
- Determine impacted memory files
- Assess change significance
- Categorize change type
- Identify related components
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 · 487 lines · 3,178 tokens per session scan A d8ff34727377
800-memory-operations-workflow is a cursor rule published in the GitHub repository savagelysubtle/BIG-BRAIN-Memory-Bank (5 stars, last pushed 1y ago), licensed MIT. It adds 3,178 tokens to every session, about $0.0159 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
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…
search-routing
Smart Search Routing — always use QMD semantic search when available, never bypass with grep for vault content.
composer-coding-excellence
Coding craft — surgical edits, convention matching, no scope creep, no slop comments, no fabricated APIs.
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.