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/creative-phase-enforcementgit 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/creative-phase-enforcement)<a href="https://agentmods.dev/rules/savagelysubtle/big-brain-memory-bank/creative-phase-enforcement"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/creative-phase-enforcement.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.00852 | $0.00852 |
| Opus 5 | $0.00426 | $0.00426 |
| Sonnet 5 | $0.00170 | $0.00170 |
| Haiku 4.5 | $0.00085 | $0.00085 |
Grade A, and why
creative-phase-enforcement 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 6d 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.
This is a copy
100% identical to creative-phase-enforcement — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CREATIVE PHASE ENFORCEMENT
TL;DR: This file establishes hard enforcement mechanisms to ensure creative phases are properly implemented for all Level 3-4 tasks and complex design decisions. It creates strict gateways that prevent implementation without documented creative phase completion.
🚨 CREATIVE PHASE GATEWAY SYSTEM
The Creative Phase Gateway prevents transition to implementation without proper creative phase documentation:
⛔ CREATIVE PHASE GATEWAY CHECK
- Level 3-4 task identified? [YES/NO]
- Complex architecture/design decisions required? [YES/NO]
- Creative phases required: [YES/NO]
→ If [YES] to any: CREATIVE PHASES REQUIRED BEFORE IMPLEMENTATION
→ NO IMPLEMENTATION PERMITTED until all required creative phases are completed
🚨 MANDATORY CREATIVE PHASE TRIGGERS
These specific scenarios REQUIRE documented creative phases before ANY implementation:
-
Component Architecture Decisions
- Component boundaries and responsibilities
- Component hierarchy and relationships
- Rendering strategies
- Composition patterns
-
State Management Approaches
- State structure design
- State update patterns
- State distribution approaches
- State persistence strategies
-
Data Modeling Decisions
- Data structure design
- Relationship modeling
- Validation approaches
- Transformation patterns
-
UI/UX Design Approaches
- Layout strategies
- Interaction patterns
- Responsive design approaches
- Accessibility implementations
-
Algorithm/Logic Design
- Business logic implementation
- Computation approaches
- Optimization strategies
- Edge case handling
🚫 IMPLEMENTATION BLOCKING
If a decision triggers ANY of the above categories:
⛔ IMPLEMENTATION BLOCKED
Creative phases MUST be completed and documented before ANY implementation code can be written.
- Decisions requiring creative phases: [List specific decisions]
- Documentation format: Full structured creative phase with markers
- Location: Document in the implementation plan before code
This is a HARD BLOCK - implementation CANNOT proceed until creative phases are properly documented.
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.
- 6d ago First seen · 122 lines · 852 tokens per session scan A 3769f3f82497
creative-phase-enforcement is a cursor rule published in the GitHub repository savagelysubtle/BIG-BRAIN-Memory-Bank (5 stars, last pushed 1y ago), licensed MIT. It adds 852 tokens to every session, about $0.0043 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to creative-phase-enforcement, differing in 0 lines, and is treated as a copy.
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.