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/templates-core)<a href="https://agentmods.dev/rules/savagelysubtle/big-brain-memory-bank/templates-core"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/templates-core/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/templates-core"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/templates-core.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.00000 | $0.01217 |
| Opus 5.5 | $0.00000 | $0.00487 |
| Sonnet 5.5 | $0.00000 | $0.00243 |
| Haiku 4.5 | $0.00000 | $0.00122 |
Grade A, and why
templates-core 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 1mo 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.
This is a copy
100% identical to templates-core — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Bank Core Templates
⚠️ ALWAYS USE THESE TEMPLATES WHEN CREATING FILES ⚠️
When creating any Memory Bank file, use these templates as the starting point. These are the ESSENTIAL templates that must be used for core files.
⚠️ REFERENCE REQUIRED: For extended and specialized templates, I MUST read templates-extended.mdc.
projectbrief.md Template
# Project Brief
## Overview
[Brief description of the project]
## Goals and Objectives
- [Primary goal 1]
- [Primary goal 2]
- [Primary goal 3]
## Requirements
- [Requirement 1]
- [Requirement 2]
- [Requirement 3]
## Constraints
- [Constraint 1]
- [Constraint 2]
## Stakeholders
- [Stakeholder 1]: [Role/Interest]
- [Stakeholder 2]: [Role/Interest]
## Success Criteria
- [Criterion 1]
- [Criterion 2]
productContext.md Template
# Product Context
## Problem Statement
[Description of the problem this project solves]
## Target Users
- [User type 1]: [Needs and expectations]
- [User type 2]: [Needs and expectations]
## User Experience Goals
- [UX goal 1]
- [UX goal 2]
## Key Features
- [Feature 1]: [Purpose and value]
- [Feature 2]: [Purpose and value]
## Workflows
[Description of key user workflows]
## Market Context
[Relevant market information, competition, etc.]
activeContext.md Template
# Active Context
## Current Focus
[Description of current development focus]
## Recent Changes
- [Change 1] - [Date]
- [Change 2] - [Date]
## Active Decisions
- [Decision 1]: [Rationale]
- [Decision 2]: [Rationale]
## Next Steps
- [Next step 1]
- [Next step 2]
## Open Questions
- [Question 1]
- [Question 2]
## Recent Completions
[Most recent completed task and next focus]
systemPatterns.md Template
# System Patterns
## Architecture Overview
[Description of system architecture]
## Key Components
- [Component 1]: [Purpose and responsibilities]
- [Component 2]: [Purpose and responsibilities]
## Design Patterns
- [Pattern 1]: [Usage and implementation]
- [Pattern 2]: [Usage and implementation]
## Data Flow
[Description of data flow through the system]
## Security Considerations
[Description of security patterns and considerations]
## Performance Considerations
[Description of performance patterns and optimizations]
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.
- 1mo ago First seen · 244 lines · 1,217 tokens per session scan A a2f87e657cb5
templates-core 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 1,217 tokens. A static security scan graded it A with 0 findings. It is 100% identical to templates-core, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
shell-first-search
Search-tool fallback when Grep/Glob hang (>30 s on Windows hosts) or are unavailable — kill the PID, retry narrower, fall back to shell grep/ls/find.
coding-process-rules
A workflow guide for handling coding tasks step by step, finishing one file before moving to the next, and recording unfinished work with TODO comments.
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.