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/documentation-standardsgit 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/documentation-standards)<a href="https://agentmods.dev/rules/savagelysubtle/big-brain-memory-bank/documentation-standards"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/documentation-standards.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.01629 | $0.01629 |
| Opus 5 | $0.00814 | $0.00814 |
| Sonnet 5 | $0.00326 | $0.00326 |
| Haiku 4.5 | $0.00163 | $0.00163 |
Grade A, and why
documentation-standards 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 5d 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TL;DR: This rule establishes consistent standards for formatting, organization, and structure of all documentation files to ensure readability, accessibility, and maintainability of project documentation.
Documentation Standards
Document Types
The documentation system consists of these primary document types:
-
Guides
- User-focused, task-oriented documents
- Provide step-by-step instructions
- Include clear examples and screenshots
- Located in
docs/Guides/
-
Reference
- API and data structure documentation
- Comprehensive feature specifications
- Technical details for implementers
- Located in
docs/Reference/
-
Architecture
- System design and components
- Data flow diagrams
- Design decisions and rationales
- Located in
docs/Architecture/
-
Tutorials
- Learning-oriented documents
- Focused on skill building
- Progressive complexity
- Located in
docs/Tutorials/
File Organization
Documentation files should follow this organizational structure:
docs/
├── Guides/ # Task-oriented instructions
│ ├── Installation.md # System installation guide
│ ├── Startup.md # System startup procedures
│ ├── Commands.md # Command reference and usage
│ └── Advanced/ # Advanced usage guides
├── Reference/ # Technical reference material
│ ├── API/ # API documentation
│ └── DataModels/ # Data structure documentation
├── Architecture/ # System architecture documentation
│ ├── Overview.md # High-level architecture
│ ├── Components.md # Component descriptions
│ └── Diagrams/ # Architecture diagrams
├── Tutorials/ # Learning-oriented materials
└── index.md # Documentation home page
Document Structure
Each document should include these sections in order:
- Title
- Clear, descriptive H1 title
- Example:
# Installation Guide
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.
- 5d ago First seen · 259 lines · 1,629 tokens per session scan A ee9d2ff4c94b
documentation-standards is a cursor rule published in the GitHub repository savagelysubtle/BIG-BRAIN-Memory-Bank (5 stars, last pushed 1y ago), licensed MIT. It adds 1,629 tokens to every session, about $0.0081 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
composer-coding-excellence
Coding craft — surgical edits, convention matching, no scope creep, no slop comments, no fabricated APIs.
composer-core
Always-on builder spine — continue the app, demoable slice, Build loop, Run/Wired handoff, ask only on high confusion weight.
composer-reasoning
High-stakes judgment for architectural or multi-option work — tradeoffs, one-way doors, reason-then-re-evaluate, honest pushback.
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.
composer-fullstack-delivery
New screen, feature, endpoint, or multi-layer slice — freeze seams, ship one demoable path, failure modes, Run/Wired handoff.