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/alkoleft/platform-context-exporterWrote 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/alkoleft/platform-context-exporter/creative-mode-map)<a href="https://agentmods.dev/rules/alkoleft/platform-context-exporter/creative-mode-map"><img src="https://agentmods.dev/badge/rules/alkoleft/platform-context-exporter/creative-mode-map/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/alkoleft/platform-context-exporter/creative-mode-map"><img src="https://agentmods.dev/badge/rules/alkoleft/platform-context-exporter/creative-mode-map.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.01826 | $0.01826 |
| Opus 5.5 | $0.00730 | $0.00730 |
| Sonnet 5.5 | $0.00365 | $0.00365 |
| Haiku 4.5 | $0.00183 | $0.00183 |
Grade A, and why
creative-mode-map 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 1mo 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-mode-map — 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CREATIVE MODE: DESIGN PROCESS MAP
TL;DR: This visual map guides the CREATIVE mode process, focusing on structured design decision-making for components that require deeper exploration before implementation.
🧭 CREATIVE MODE PROCESS FLOW
graph TD
Start["START CREATIVE MODE"] --> ReadTasks["Read tasks.md<br>For Creative Requirements"]
%% Initial Assessment
ReadTasks --> VerifyPlan{"Plan Complete<br>& Creative Phases<br>Identified?"}
VerifyPlan -->|"No"| ReturnPlan["Return to<br>PLAN Mode"]
VerifyPlan -->|"Yes"| IdentifyPhases["Identify Creative<br>Phases Required"]
%% Creative Phase Selection
IdentifyPhases --> SelectPhase["Select Next<br>Creative Phase"]
SelectPhase --> PhaseType{"Creative<br>Phase Type?"}
%% Creative Phase Types
PhaseType -->|"UI/UX<br>Design"| UIPhase["UI/UX CREATIVE PHASE<br>Core/creative-phase-uiux.md"]
PhaseType -->|"Architecture<br>Design"| ArchPhase["ARCHITECTURE CREATIVE PHASE<br>Core/creative-phase-architecture.md"]
PhaseType -->|"Data Model<br>Design"| DataPhase["DATA MODEL CREATIVE PHASE<br>Core/creative-phase-data.md"]
PhaseType -->|"Algorithm<br>Design"| AlgoPhase["ALGORITHM CREATIVE PHASE<br>Core/creative-phase-algorithm.md"]
%% UI/UX Creative Phase
UIPhase --> UI_Problem["Define UI/UX<br>Problem"]
UI_Problem --> UI_Research["Research UI<br>Patterns"]
UI_Research --> UI_Options["Explore UI<br>Options"]
UI_Options --> UI_Evaluate["Evaluate User<br>Experience"]
UI_Evaluate --> UI_Decision["Make Design<br>Decision"]
UI_Decision --> UI_Document["Document UI<br>Design"]
%% Architecture Creative Phase
ArchPhase --> Arch_Problem["Define Architecture<br>Challenge"]
Arch_Problem --> Arch_Options["Explore Architecture<br>Options"]
Arch_Options --> Arch_Analyze["Analyze Tradeoffs"]
Arch_Analyze --> Arch_Decision["Make Architecture<br>Decision"]
Arch_Decision --> Arch_Document["Document<br>Architecture"]
Arch_Document --> Arch_Diagram["Create Architecture<br>Diagram"]
%% Data Model Creative Phase
DataPhase --> Data_Requirements["Define Data<br>Requirements"]
Data_Requirements --> Data_Structure["Design Data<br>Structure"]
Data_Structure --> Data_Relations["Define<br>Relationships"]
Data_Relations --> Data_Validation["Design<br>Validation"]
Data_Validation --> Data_Document["Document<br>Data Model"]
%% Algorithm Creative Phase
AlgoPhase --> Algo_Problem["Define Algorithm<br>Problem"]
Algo_Problem --> Algo_Options["Explore Algorithm<br>Approaches"]
Algo_Options --> Algo_Evaluate["Evaluate Time/Space<br>Complexity"]
Algo_Evaluate --> Algo_Decision["Make Algorithm<br>Decision"]
Algo_Decision --> Algo_Document["Document<br>Algorithm"]
%% Documentation & Completion
UI_Document & Arch_Diagram & Data_Document & Algo_Document --> CreateDoc["Create Creative<br>Phase Document"]
CreateDoc --> UpdateTasks["Update tasks.md<br>with Decision"]
UpdateTasks --> MorePhases{"More Creative<br>Phases?"}
MorePhases -->|"Yes"| SelectPhase
MorePhases -->|"No"| VerifyComplete["Verify All<br>Phases Complete"]
VerifyComplete --> NotifyComplete["Signal Creative<br>Phases Complete"]
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.
- 1mo ago First seen · 224 lines · 1,826 tokens per session scan A 057f538ace5b
creative-mode-map is a cursor rule published in the GitHub repository alkoleft/platform-context-exporter (49 stars, last pushed 1y ago), licensed MIT. It adds 1,826 tokens to every session, about $0.0073 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to creative-mode-map, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
creative-phase-uiux
UI/UX Design Guidelines and Process for the Creative Phase.
creative-mode-map
Visual process map for CREATIVE mode (Design Decisions).
optimized-creative-template
Optimized creative phase template with progressive documentation.
1c-coding-standards
Coding standards for BSL, the programming language used by the 1C business software platform. They cover naming, method documentation, database queries, collections, client-server code, and performance practices.
bsl-ssl
A set of rules for developing 1C applications built on БСП, the Russian-language Standard Subsystems Library. It tells developers when to reuse library functionality, how to mark changes, and how to handle outdated objects.
1c-mdo-integrity
Rules for keeping 1C EDT MDO files structurally valid. MDO files describe configuration objects, and the rules cover unique identifiers and valid links between objects.