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/140-unified-command-interfacegit 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/140-unified-command-interface)<a href="https://agentmods.dev/rules/savagelysubtle/big-brain-memory-bank/140-unified-command-interface"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/140-unified-command-interface.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.03595 | $0.03595 |
| Opus 5 | $0.01798 | $0.01798 |
| Sonnet 5 | $0.00719 | $0.00719 |
| Haiku 4.5 | $0.00360 | $0.00360 |
Grade A, and why
140-unified-command-interface 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 — 541 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TL;DR: The Unified Command Interface provides a standardized command structure for all Memory Bank operations, ensuring consistent interaction patterns and predictable behavior across different contexts.
1.0.0
```
BIG [category] [command] [parameters] [--options]
```
Where:
- **BIG**: Universal command prefix indicating Memory Bank operation
- **category**: Functional area (memory, workflow, verification, etc.)
- **command**: Specific operation within the category
- **parameters**: Required command inputs in fixed order
- **options**: Optional flags modifying command behavior
Examples:
```
BIG memory read projectbrief.md --section requirements
BIG workflow plan "Database schema design" --complexity 3
BIG verify consistency --focus architecture
```
This structure ensures consistent command patterns across all interactions.
1. **memory**
- Core memory file operations
- Example: `BIG memory update activeContext.md`
2. **workflow**
- Task process management
- Example: `BIG workflow start act-mode`
3. **verify**
- Verification and validation
- Example: `BIG verify consistency`
4. **system**
- System configuration and management
- Example: `BIG system status`
5. **bedtime**
- Bedtime protocol operations
- Example: `BIG bedtime prepare`
6. **help**
- Documentation and assistance
- Example: `BIG help commands`
7. **creative**
- Creative phase operations
- Example: `BIG creative evaluate design1.md`
Each category has standardized commands and parameter patterns.
**Memory Operations**
- `BIG memory read [file] [--section] [--format]`
- `BIG memory write [file] [content] [--append]`
- `BIG memory update [file] [--section] [content]`
- `BIG memory search [query] [--files] [--context]`
- `BIG memory list [--type] [--status]`
**Workflow Operations**
- `BIG workflow start [mode] [--complexity]`
- `BIG workflow switch [mode]`
- `BIG workflow status`
- `BIG workflow track [section] [--status]`
- `BIG workflow checkpoint [description]`
**Verification Operations**
- `BIG verify files [--focus]`
- `BIG verify consistency [--scope]`
- `BIG verify references [--file]`
- `BIG verify structure [--files]`
- `BIG verify health [--detail]`
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 · 541 lines · 3,595 tokens per session scan A 1b9925c3fefb
140-unified-command-interface 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,595 tokens to every session, about $0.0180 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.