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/401-documentation-organization)<a href="https://agentmods.dev/rules/savagelysubtle/big-brain-memory-bank/401-documentation-organization"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/401-documentation-organization.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.00000 | $0.01266 |
| Opus 5 | $0.00000 | $0.00633 |
| Sonnet 5 | $0.00000 | $0.00253 |
| Haiku 4.5 | $0.00000 | $0.00127 |
Grade A, and why
401-documentation-organization 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 8d 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: WHEN adding new documentation, PLACE files in correct predefined folder structure, MAINTAIN organization. globs: docs/**/*.md
<folder path="docs/domain/">
<description>Domain model and business rules documentation</description>
<contents>
<file>entities.md</file>
<file>models.md</file>
<file>services.md</file>
<file>repositories.md</file>
</contents>
</folder>
<folder path="docs/infrastructure/">
<description>Infrastructure implementation details</description>
<subfolders>
<folder path="docs/infrastructure/fs/">
<description>File system implementation documentation</description>
</folder>
<folder path="docs/infrastructure/parsing/">
<description>Document parsing implementation</description>
</folder>
<folder path="docs/infrastructure/ai/">
<description>AI integration implementation</description>
</folder>
</subfolders>
</folder>
<folder path="docs/interfaces/">
<description>Interface layer documentation</description>
<subfolders>
<folder path="docs/interfaces/api/">
<description>API documentation</description>
</folder>
<folder path="docs/interfaces/cli/">
<description>Command line interface documentation</description>
</folder>
<folder path="docs/interfaces/output/">
<description>Output format documentation</description>
</folder>
<folder path="docs/interfaces/ingest/">
<description>Data ingestion documentation</description>
</folder>
</subfolders>
</folder>
<folder path="docs/guides/">
<description>User and developer guides</description>
<contents>
<file>getting-started.md</file>
<file>installation.md</file>
<file>configuration.md</file>
<file>development.md</file>
</contents>
</folder>
<folder path="docs/api-reference/">
<description>API reference documentation</description>
</folder>
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.
- 8d ago First seen · 204 lines · 0 tokens per session scan A 277daf9aef71
401-documentation-organization 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,266 tokens. 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-core
Always-on builder spine — continue the app, demoable slice, Build loop, Run/Wired handoff, ask only on high confusion weight.
composer-coding-excellence
Coding craft — surgical edits, convention matching, no scope creep, no slop comments, no fabricated APIs.
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.