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/150-standard-initialization-procedure)<a href="https://agentmods.dev/rules/savagelysubtle/big-brain-memory-bank/150-standard-initialization-procedure"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/150-standard-initialization-procedure/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/150-standard-initialization-procedure"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/150-standard-initialization-procedure.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.03229 | $0.03229 |
| Opus 5.5 | $0.01292 | $0.01292 |
| Sonnet 5.5 | $0.00646 | $0.00646 |
| Haiku 4.5 | $0.00323 | $0.00323 |
Grade A, and why
150-standard-initialization-procedure 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 2mo 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 — 499 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TL;DR: The Standard Initialization Procedure provides a systematic process for memory bank initialization at the beginning of each session, ensuring complete context restoration despite memory reset.
1.0.0
1. **Identity Confirmation**
- Establish BIG BRAIN identity
- Acknowledge memory reset
- Recognize memory bank dependency
- Set operational parameters
2. **Memory Bank Loading**
- Locate core memory files
- Load essential context documents
- Verify file availability
- Establish memory structure
3. **Context Restoration**
- Process project brief
- Understand product context
- Absorb active context
- Comprehend system patterns
- Assimilate technical context
- Review progress status
4. **Verification Execution**
- Perform file verification
- Execute consistency checks
- Validate references
- Assess memory health
- Generate verification report
5. **Task Contextualization**
- Determine current focus
- Assess task complexity
- Select appropriate workflow
- Establish operational mode
- Identify relevant patterns
6. **Readiness Confirmation**
- Confirm complete context loading
- Verify memory bank health
- Establish system capabilities
- Note any limitations
- Declare initialization complete
This sequence ensures systematic restoration of complete operational context.
1. **projectbrief.md**
- Foundation document
- Core requirements
- Project goals and scope
- Success criteria
2. **productContext.md**
- Problem space
- User experience goals
- Value proposition
- Market context
3. **activeContext.md**
- Current work focus
- Recent changes
- Next steps
- Open issues
4. **systemPatterns.md**
- System architecture
- Component relationships
- Implementation patterns
- Design decisions
5. **techContext.md**
- Technology stack
- Development environment
- Technical constraints
- Integration points
6. **progress.md**
- Implementation status
- Feature completeness
- Known issues
- Future milestones
These files provide the essential context required for operation.
```
BIG initialize [task] [--complexity=1-4] [--mode=plan|act] [--focus=area]
```
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.
- 2mo ago First seen · 499 lines · 3,229 tokens per session scan A 09f5d9e2c57f
150-standard-initialization-procedure 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,229 tokens to every session, about $0.0129 per session on Opus 5.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".
search-routing
Smart Search Routing — always use QMD semantic search when available, never bypass with grep for vault content.
web
Web build conventions (separate from native and RN JS).
components
Component patterns and UI conventions.
git
Git workflow and commit conventions.
approved-plan-execution
Guard execution of an approved plan or burndown: forbid reward hacking and feature deletion; require checkpoints, context discipline, safe terminal use, and fresh verification. Applies to approved plan-.md, complete-everything, and burndown-full runs, whatever model runs them.