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/180-creative-process-structuregit 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/180-creative-process-structure)<a href="https://agentmods.dev/rules/savagelysubtle/big-brain-memory-bank/180-creative-process-structure"><img src="https://agentmods.dev/badge/rules/savagelysubtle/big-brain-memory-bank/180-creative-process-structure.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.00000 | $0.04739 |
| Opus 5 | $0.00000 | $0.02370 |
| Sonnet 5 | $0.00000 | $0.00948 |
| Haiku 4.5 | $0.00000 | $0.00474 |
Grade A, and why
180-creative-process-structure 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 — 780 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: WHEN approaching design-intensive tasks APPLY structured creative processes globs: ["/*.md", "/*.mdc"] alwaysApply: true
TL;DR: The Creative Process Structure provides systematic approaches for design-intensive tasks, ensuring thorough problem analysis, exploration, evaluation, and verification for optimal solutions.
1.0.0
1. **Architecture Design**
- Purpose: System-wide structure and component relationships
- Focus: Subsystem organization, interaction patterns, data flow
- Primary concerns: Scalability, maintainability, flexibility
- Artifacts: Architecture diagrams, component specifications, integration models
2. **Component Design**
- Purpose: Individual module implementation approach
- Focus: Internal structure, algorithms, data organization
- Primary concerns: Performance, reliability, testability
- Artifacts: Component specifications, interface definitions, behavior models
3. **Algorithm Design**
- Purpose: Specialized processing logic
- Focus: Computational efficiency, correctness, edge cases
- Primary concerns: Complexity, accuracy, optimization
- Artifacts: Algorithm specifications, flowcharts, pseudocode, complexity analysis
4. **Data Model Design**
- Purpose: Information organization and relationships
- Focus: Entity relationships, schema structure, access patterns
- Primary concerns: Integrity, flexibility, efficiency
- Artifacts: Entity-relationship diagrams, schema definitions, access pattern documentation
5. **UI/UX Design**
- Purpose: User interaction and experience
- Focus: User flows, interface elements, information presentation
- Primary concerns: Usability, clarity, accessibility
- Artifacts: Wireframes, user flows, interaction specifications
Each design type has specialized process adaptations.
1. **Problem Analysis**
- Understand requirements and constraints
- Analyze context and stakeholder needs
- Identify success criteria
- Recognize quality factors
2. **Exploration**
- Generate multiple solution approaches
- Research relevant patterns and precedents
- Consider alternative strategies
- Leverage different perspectives
3. **Evaluation**
- Assess alternatives against criteria
- Consider tradeoffs and implications
- Analyze risks and challenges
- Project implementation complexity
4. **Selection**
- Choose optimal approach
- Document decision rationale
- Address risks and concerns
- Define implementation strategy
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 · 780 lines · 0 tokens per session scan A a42480568f19
180-creative-process-structure 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 4,739 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.
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.