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/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/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/workflow-examples"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/workflow-examples.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.02038 |
| Opus 5.5 | $0.00000 | $0.00815 |
| Sonnet 5.5 | $0.00000 | $0.00408 |
| Haiku 4.5 | $0.00000 | $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 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 workflow-examples — 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 — 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.
- 1mo ago 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 costs nothing until one of its globs matches a file; then it loads 2,038 tokens. A static security scan graded it A with 0 findings. It is 100% identical to workflow-examples, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
_project
Project-wide conventions and developer environment context (RN monorepo, no-Mac dev).
monorepo-and-tooling
Rules for projects that may use a monorepo, a single repository containing multiple applications or shared packages. They also define Taskfile commands and how to keep environment settings outside the code.
client-workflow-bootstrap
Cursor rule "client-workflow-bootstrap" from ulises-jeremias/agent-toolkit, covering agent vs skill rule — why agent (cite clause), when to use vs holistic, caller / skills / handoff, interview process and gate before generating.
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.