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/040-enhanced-complexity-frameworkgit 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/040-enhanced-complexity-framework)<a href="https://agentmods.dev/rules/savagelysubtle/big-brain-memory-bank/040-enhanced-complexity-framework"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/040-enhanced-complexity-framework.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 | $0.00000 | $0.02546 |
| Opus 5 | $0.00000 | $0.01273 |
| Sonnet 5 | $0.00000 | $0.00509 |
| Haiku 4.5 | $0.00000 | $0.00255 |
Grade A, and why
040-enhanced-complexity-framework 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 — 359 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: WHEN assessing task complexity ENSURE appropriate process rigor is applied globs: ["/*.md", "/*.mdc"] alwaysApply: true
TL;DR: The Enhanced Complexity Framework provides objective criteria for assessing task complexity and selecting the appropriate level of process rigor.
1.0.0
1. **Scope**
- What is the breadth of the system affected?
- How many components or modules are impacted?
- How many interfaces need to change?
- What is the scope of testing required?
2. **Risk**
- What is the potential impact of failure?
- How critical is the affected functionality?
- What is the security sensitivity of affected areas?
- What is the visibility to users or other systems?
3. **Dependencies**
- How many dependencies exist between components?
- Are there external system dependencies?
- What is the complexity of the dependency network?
- Are there timing or sequencing dependencies?
4. **Technical Difficulty**
- What is the algorithmic complexity?
- How sophisticated is the solution required?
- What level of specialized knowledge is needed?
- Are there performance considerations or constraints?
Each factor is rated from Level 1 (low) to Level 4 (extreme). The highest level among the factors determines the overall complexity level.
**Level 1: Simple**
- **Scope**: Single function or small feature
- **Risk**: Minimal impact, isolated change
- **Dependencies**: Few or no dependencies
- **Difficulty**: Straightforward implementation
- **Example**: Bug fix, small feature enhancement, documentation update
**Level 2: Moderate**
- **Scope**: Single component or module
- **Risk**: Limited impact, contained to feature area
- **Dependencies**: Moderate dependencies within system
- **Difficulty**: Standard implementation techniques
- **Example**: New feature, component enhancement, API addition
**Level 3: Complex**
- **Scope**: Multiple components or modules
- **Risk**: Significant impact, affects key functionality
- **Dependencies**: Multiple dependencies, some external
- **Difficulty**: Advanced implementation, specialized knowledge
- **Example**: Major feature, integration with external system, security enhancement
**Level 4: Critical**
- **Scope**: System-wide or architectural changes
- **Risk**: Critical impact, core functionality affected
- **Dependencies**: Complex network of dependencies
- **Difficulty**: Cutting-edge implementation, deep expertise required
- **Example**: Architectural redesign, core system replacement, platform migration
The highest level among the four factors determines the overall complexity level.
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 · 359 lines · 0 tokens per session scan A 392afeaf33e1
040-enhanced-complexity-framework 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 2,546 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-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.
clarify-first
Infer-and-act by default — ask only on high confusion weight, after inspecting, with a decision-linked question.
composer-reasoning
High-stakes judgment for architectural or multi-option work — tradeoffs, one-way doors, reason-then-re-evaluate, honest pushback.
composer-debugging
Root-cause debugging — reproduce, trace data flow, test cheapest hypothesis, fix the cause not the symptom.
composer-deep-research
Edge-case research for audits, vendor comparisons, and unfamiliar APIs — primaries first, iterative retrieval, explicit conflicts; not the default build path.