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/workflow-examplesgit 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/workflow-examples)<a href="https://agentmods.dev/rules/savagelysubtle/big-brain-memory-bank/workflow-examples"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/workflow-examples.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.02038 | $0.02038 |
| Opus 5 | $0.01019 | $0.01019 |
| Sonnet 5 | $0.00408 | $0.00408 |
| Haiku 4.5 | $0.00204 | $0.00204 |
Grade A, and why
workflow-examples 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 today.
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 — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Implementation Examples
INITIALIZATION Examples
Example (MUST FOLLOW THIS FORMAT):
## INITIALIZATION
Task: Implement User Authentication System
Objective: Create secure login functionality with JWT token support
[X] Review all Memory Bank files complete
[X] .cursorrules file created/reviewed
[X] tasks.md file verified/created
[ ] Documentation setup pending
[ ] Task planning pending
[ ] Implementation pending
[ ] Reflection pending
[ ] Archiving pending
## Section Header Tracking
[ ] INITIALIZATION
[ ] DOCUMENTATION SETUP
[ ] TASK PLANNING
[ ] IMPLEMENTATION
[ ] REFLECTION
[ ] ARCHIVING
## Verification Commitment
I WILL run the full verification checklist before completing this task.
I will maintain tasks.md as the single source of truth for task status.
DOCUMENTATION SETUP Examples
Example (MUST FOLLOW THIS FORMAT):
## DOCUMENTATION SETUP
After reviewing the Memory Bank files, I've updated the following:
[X] Updated systemPatterns.md with authentication flow design:
- Added JWT authentication sequence diagram
- Documented token refresh mechanism
- Added security considerations for authentication
[X] Updated techContext.md with JWT library requirements:
- Added jsonwebtoken dependency
- Added bcrypt for password hashing
- Added dotenv for environment variable management
[X] Updated activeContext.md with implementation plan:
- Added current focus on authentication system
- Documented key decisions on token expiration
- Added next steps after authentication is complete
[X] Updated progress.md with authentication milestones:
- Added authentication system as in-progress feature
- Documented dependencies on database setup
- Added success criteria for authentication feature
[X] Updated tasks.md with authentication tasks:
- Added main authentication task with [ ] marker
- Added subtasks for registration, login, and middleware
- Set initial task priority and deadlines
[X] Updated .cursorrules with project-specific patterns:
- Added authentication naming conventions
- Documented password validation requirements
- Added security validation patterns
## Section Header Tracking
[X] INITIALIZATION
[X] DOCUMENTATION SETUP
[ ] TASK PLANNING
[ ] IMPLEMENTATION
[ ] REFLECTION
[ ] ARCHIVING
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.
- today First seen · 335 lines · 2,038 tokens per session scan A 4cfeaf46a645
workflow-examples 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,038 tokens to every session, about $0.0102 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-09-03.
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.
clarify-first
Infer-and-act by default — ask only on high confusion weight, after inspecting, with a decision-linked question.
memory-protocol
记忆系统 — 召回、写入、维护、防丢失的完整协议.
user-context
用户信息 — 关于你服务的主人.