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/diagram-standards)<a href="https://agentmods.dev/rules/savagelysubtle/big-brain-memory-bank/diagram-standards"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/diagram-standards/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/diagram-standards"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/diagram-standards.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.01822 | $0.01822 |
| Opus 5 | $0.00911 | $0.00911 |
| Sonnet 5 | $0.00364 | $0.00364 |
| Haiku 4.5 | $0.00182 | $0.00182 |
Grade A, and why
diagram-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 10d 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 — 219 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 creating, formatting, and using Mermaid diagrams in the project to ensure visual consistency, maintainability, and proper integration with documentation.
Mermaid Diagram Standards
1.0.0
File Organization
Mermaid diagrams should follow this organizational structure:
project-root/
├── images/ # Main images directory
│ ├── *.mermaid # Source Mermaid files
│ ├── *.png # Rendered PNG images
│ └── *.svg # Rendered SVG images (preferred)
├── docs/
│ ├── assets/ # Documentation-specific images
│ │ ├── *.mermaid # Source files for doc-specific diagrams
│ │ ├── *.png # Rendered images
│ │ └── *.svg # Rendered SVG images
Diagram Types and Usage
Use appropriate diagram types for specific content:
- Flowcharts
- Use for: processes, workflows, decision trees
- Direction: TD (top-down) for processes, LR (left-right) for timelines
- Example use: Memory initialization process, command execution flow
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.
- 10d ago First seen · 219 lines · 1,822 tokens per session scan A 7d4cbf132261
diagram-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,822 tokens to every session, about $0.0091 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
components
Component patterns and UI conventions.
tailwind
Tailwind CSS and styling conventions.
components
Rules for component usage - which component libraries are allowed (shadcn/ui, Aceternity, Kibo, Magic UI, etc.), reuse over recreation, table implementation standards, and component modularization for both new features and existing components.
designer
Cursor rule "designer" from ulises-jeremias/agent-toolkit, covering designer, when invoked, design routing — canonical (do not run mechanically), figma subtree and delegate to skills.
web
Web build conventions (separate from native and RN JS).
git
Git workflow and commit conventions.