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/520-rule-visibility-system)<a href="https://agentmods.dev/rules/savagelysubtle/big-brain-memory-bank/520-rule-visibility-system"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/520-rule-visibility-system/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/520-rule-visibility-system"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/520-rule-visibility-system.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.02931 | $0.02931 |
| Opus 5 | $0.01465 | $0.01465 |
| Sonnet 5 | $0.00586 | $0.00586 |
| Haiku 4.5 | $0.00293 | $0.00293 |
Grade A, and why
520-rule-visibility-system 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 9d 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 — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TL;DR: The Rule Visibility System provides tools to visualize active rules, understand rule execution, and debug rule-related issues, enhancing transparency of the BIG BRAIN rule system.
1.0.0
1. **"SHOW ACTIVE RULES"**
- Lists all currently active rules
- Groups rules by category
- Shows rule activation status
- Indicates which rules are applying to current context
- Provides count summary by category
2. **"SHOW ACTIVE RULES [CATEGORY]"**
- Lists active rules in the specified category
- Shows detailed information for category rules
- Provides category-specific statistics
- Examples:
- "SHOW ACTIVE RULES FOUNDATION"
- "SHOW ACTIVE RULES VERIFICATION"
- "SHOW ACTIVE RULES UTILITIES"
3. **"DEBUG RULES"**
- Performs comprehensive rule system diagnostics
- Identifies potential conflicts
- Shows rule execution statistics
- Reports on rule health
- Recommends optimizations
4. **"DEBUG RULE [RULE_NAME]"**
- Provides detailed analysis of specific rule
- Shows rule execution history
- Identifies interaction with other rules
- Examples:
- "DEBUG RULE memory-file-verification"
- "DEBUG RULE workflow-orchestration"
These commands enable effective navigation and inspection of the rule system.
1. **Category Hierarchy**
```
BIG BRAIN RULE SYSTEM
├── Core Rules (32 active)
│ ├── Foundation (12 active)
│ ├── Verification (8 active)
│ ├── Command (6 active)
│ └── Creative (6 active)
├── Protocols (5 active)
├── Utilities (4 active)
└── Templates (1 active)
```
2. **Rule Status Table**
```
| Rule ID | Name | Category | Status | Applied | Last Used |
|---------|-------------------------|-------------|---------|---------|-----------|
| 040 | complexity-framework | Foundation | Active | Yes | Just now |
| 100 | file-verification | Verification| Active | Yes | 2m ago |
| 180 | creative-process | Creative | Active | No | 1h ago |
| 500 | organization-enforcer | Utilities | Active | Yes | 5m ago |
```
3. **Detailed Rule Card**
```
┌─────────────────────────────────────────────────────┐
│ RULE: 100-memory-file-verification.mdc │
├─────────────────────────────────────────────────────┤
│ Category: Verification Framework │
│ Version: 1.0.0 │
│ Status: Active │
│ Applies To: **/*.md, **/*.mdc │
│ Always Apply: true │
│ Last Applied: 2 minutes ago │
│ Application Count: 47 times this session │
│ Related Rules: file-consistency-check, error-recovery│
└─────────────────────────────────────────────────────┘
```
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.
- 9d ago First seen · 376 lines · 2,931 tokens per session scan A cf1b0021403d
520-rule-visibility-system is a cursor rule published in the GitHub repository savagelysubtle/BIG-BRAIN-Memory-Bank (5 stars, last pushed 1y ago), licensed MIT. It adds 2,931 tokens to every session, about $0.0147 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-debugging
Root-cause debugging — reproduce, trace data flow, test cheapest hypothesis, fix the cause not the symptom.
performance
Performance: profiling-first optimization, caching, bottleneck patterns.
error-handling
Error handling: typed errors, boundaries, user messages.
error-handling
Error handling patterns for backend services. Apply when handling errors in handlers or services.
minimax-m3-self-evolution
MiniMax M3 self-evolution harness: iterative refinement loops, compress-before-iterate, autonomous debugging, and recursive improvement patterns.
composer-coding-excellence
Coding craft — surgical edits, convention matching, no scope creep, no slop comments, no fabricated APIs.