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/creative-phase-triggers)<a href="https://agentmods.dev/rules/savagelysubtle/big-brain-memory-bank/creative-phase-triggers"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/creative-phase-triggers.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.01425 | $0.01425 |
| Opus 5 | $0.00713 | $0.00713 |
| Sonnet 5 | $0.00285 | $0.00285 |
| Haiku 4.5 | $0.00143 | $0.00143 |
Grade A, and why
creative-phase-triggers 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.
This is a copy
100% identical to creative-phase-triggers — 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CREATIVE PHASE TRIGGERS & TRANSITIONS
TL;DR: Recognize when a task requires dedicated creative thinking and explicitly enter a creative phase. This document explains how to identify creative phase triggers, how to transition into/out of creative phases, and how to select the appropriate creative phase type based on the problem.
🔍 WHEN TO ENTER A CREATIVE PHASE
Enter a creative phase whenever you encounter:
- Multiple viable approaches to solving a problem with significant trade-offs
- Complex design decisions that require systematic analysis
- Problems with competing constraints that need careful balancing
- Tasks requiring exploration of multiple options before implementation
- Situations where decisions have far-reaching consequences
- Architecture or algorithm planning that impacts multiple components
Specific Triggers by Domain
Algorithm Design Triggers
- Implementing a complex algorithm with performance constraints
- Designing data structures for specialized use cases
- Working with tree, graph, or dynamic programming problems
- Optimizing existing algorithms with specific constraints
- Creating new computational approaches
UI/UX Design Triggers
- Designing layouts with complex information hierarchy
- Creating component structures with extensive state management
- Designing responsive interfaces with complex constraints
- Planning complex user flows
- Addressing accessibility and usability challenges
Architecture Planning Triggers
- Designing service boundaries and communication patterns
- Creating data storage and access strategies
- Planning security and authentication systems
- Designing for scalability and resilience
- Creating deployment and infrastructure models
🚨 MANDATORY CREATIVE PHASES FOR LEVEL 3-4 TASKS
Creative phases are NOT optional for Level 3-4 tasks. They MUST be used for:
- All component architecture decisions in Level 3-4 tasks
- All state management approaches in Level 3-4 tasks
- All UI/UX design decisions affecting multiple components
- All data modeling decisions with system-wide implications
- Any algorithm implementation with performance or scalability requirements
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 · 187 lines · 1,425 tokens per session scan A 8ad354600362
creative-phase-triggers 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,425 tokens to every session, about $0.0071 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to creative-phase-triggers, differing in 0 lines, and is treated as a copy.
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.