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/optimized-creative-template)<a href="https://agentmods.dev/rules/alkoleft/platform-context-exporter/optimized-creative-template"><img src="https://agentmods.dev/badge/rules/alkoleft/platform-context-exporter/optimized-creative-template/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/optimized-creative-template"><img src="https://agentmods.dev/badge/rules/alkoleft/platform-context-exporter/optimized-creative-template.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.01563 | $0.01563 |
| Opus 5.5 | $0.00625 | $0.00625 |
| Sonnet 5.5 | $0.00313 | $0.00313 |
| Haiku 4.5 | $0.00156 | $0.00156 |
Grade A, and why
optimized-creative-template 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 optimized-creative-template — 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OPTIMIZED CREATIVE PHASE TEMPLATE
TL;DR: This template implements a progressive documentation approach for creative phases, optimizing token usage while maintaining thorough design exploration.
📝 PROGRESSIVE DOCUMENTATION MODEL
graph TD
Start["Creative Phase Start"] --> P1["1️⃣ PROBLEM<br>Define scope"]
P1 --> P2["2️⃣ OPTIONS<br>Explore alternatives"]
P2 --> P3["3️⃣ ANALYSIS<br>Evaluate selected options"]
P3 --> P4["4️⃣ DECISION<br>Finalize approach"]
P4 --> P5["5️⃣ IMPLEMENTATION<br>Document guidelines"]
style Start fill:#d971ff,stroke:#a33bc2,color:white
style P1 fill:#4da6ff,stroke:#0066cc,color:white
style P2 fill:#ffa64d,stroke:#cc7a30,color:white
style P3 fill:#4dbb5f,stroke:#36873f,color:white
style P4 fill:#d94dbb,stroke:#a3378a,color:white
style P5 fill:#4dbbbb,stroke:#368787,color:white
📋 TEMPLATE STRUCTURE
📌 CREATIVE PHASE START: [Component Name]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1️⃣ PROBLEM
Description: [Brief problem description]
Requirements: [Key requirements as bullet points]
Constraints: [Technical or business constraints]
2️⃣ OPTIONS
Option A: [Name] - [One-line description]
Option B: [Name] - [One-line description]
Option C: [Name] - [One-line description]
3️⃣ ANALYSIS
| Criterion | Option A | Option B | Option C |
|-----------|----------|----------|----------|
| Performance | ⭐⭐⭐ | ⭐⭐ | ⭐⭐⭐⭐ |
| Complexity | ⭐⭐ | ⭐⭐⭐ | ⭐⭐⭐⭐ |
| Maintainability | ⭐⭐⭐⭐ | ⭐⭐⭐ | ⭐⭐ |
Key Insights:
- [Insight 1]
- [Insight 2]
4️⃣ DECISION
Selected: [Option X]
Rationale: [Brief justification]
5️⃣ IMPLEMENTATION NOTES
- [Implementation note 1]
- [Implementation note 2]
- [Implementation note 3]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📌 CREATIVE PHASE END
🧩 DETAILED OPTION ANALYSIS (ON DEMAND)
Detailed analysis can be provided on demand for selected options:
<details>
<summary>Detailed Analysis: Option A</summary>
### Option A: [Full Name]
**Complete Description**:
[Detailed description of how the option works]
**Pros**:
- [Pro 1 with explanation]
- [Pro 2 with explanation]
- [Pro 3 with explanation]
**Cons**:
- [Con 1 with explanation]
- [Con 2 with explanation]
**Implementation Complexity**: [Low/Medium/High]
[Explanation of complexity factors]
**Resource Requirements**:
[Details on resource needs]
**Risk Assessment**:
[Analysis of risks]
</details>
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 · 219 lines · 1,563 tokens per session scan A bee7fbd9e4d0
optimized-creative-template is a cursor rule published in the GitHub repository alkoleft/platform-context-exporter (48 stars, last pushed 1y ago), licensed MIT. It adds 1,563 tokens to every session, about $0.0063 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to optimized-creative-template, 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.
code-review-checklist
A code-review checklist for 1C source files, including BSL and OS files. It groups findings by severity and checks issues such as security, performance, errors, access control, duplication, and maintainability.
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.