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/alkoleft/platform-context-exporter/creative-phase-enforcementgit clone --depth 1 https://github.com/alkoleft/platform-context-exporterWhat 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 | $0.00000 | $0.01123 |
| Opus 5 | $0.00000 | $0.00562 |
| Sonnet 5 | $0.00000 | $0.00225 |
| Haiku 4.5 | $0.00000 | $0.00112 |
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 3d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CREATIVE PHASE ENFORCEMENT
TL;DR: This document implements strict enforcement of creative phase requirements for Level 3-4 tasks, ensuring all design decisions are properly documented and verified before implementation can proceed.
🔍 ENFORCEMENT WORKFLOW
graph TD
Start["Task Start"] --> Check{"Level 3-4<br>Task?"}
Check -->|Yes| Analyze["Analyze Design<br>Decision Points"]
Check -->|No| Optional["Creative Phase<br>Optional"]
Analyze --> Decision{"Design Decisions<br>Required?"}
Decision -->|Yes| Gate["🚨 IMPLEMENTATION<br>BLOCKED"]
Decision -->|No| Allow["Allow<br>Implementation"]
Gate --> Creative["Enter Creative<br>Phase"]
Creative --> Verify{"All Decisions<br>Documented?"}
Verify -->|No| Return["Return to<br>Creative Phase"]
Verify -->|Yes| Proceed["Allow<br>Implementation"]
style Start fill:#4da6ff,stroke:#0066cc,color:white
style Check fill:#ffa64d,stroke:#cc7a30,color:white
style Analyze fill:#4dbb5f,stroke:#36873f,color:white
style Gate fill:#d94dbb,stroke:#a3378a,color:white
style Creative fill:#4dbbbb,stroke:#368787,color:white
style Verify fill:#d971ff,stroke:#a33bc2,color:white
🚨 ENFORCEMENT GATES
graph TD
subgraph "CREATIVE PHASE GATES"
G1["Entry Gate<br>Verify Requirements"]
G2["Process Gate<br>Verify Progress"]
G3["Exit Gate<br>Verify Completion"]
end
G1 --> G2 --> G3
style G1 fill:#4dbb5f,stroke:#36873f,color:white
style G2 fill:#ffa64d,stroke:#cc7a30,color:white
style G3 fill:#d94dbb,stroke:#a3378a,color:white
📋 ENFORCEMENT CHECKLIST
## Entry Gate Verification
- [ ] Task complexity is Level 3-4
- [ ] Design decisions identified
- [ ] Creative phase requirements documented
- [ ] Required participants notified
## Process Gate Verification
- [ ] All options being considered
- [ ] Pros/cons documented
- [ ] Technical constraints identified
- [ ] Implementation impacts assessed
## Exit Gate Verification
- [ ] All decisions documented
- [ ] Rationale provided for choices
- [ ] Implementation plan outlined
- [ ] Verification against 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.
- 3d ago First seen · 145 lines · 0 tokens per session scan A be78abebc5d5
creative-phase-enforcement is a cursor rule published in the GitHub repository alkoleft/platform-context-exporter (48 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,123 tokens. 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
1c-coding-standards
Стандарты кода BSL: именование, запросы, коллекции.
anti_patterns
Критические антипаттерны 1С: запрос в цикле, реквизиты через точку.
bsl-ssl
Переиспользование БСП, разметка правок типовых модулей, устаревшие объекты.
sdd-workflow
Specification-Driven Development: 9-фазный workflow разработки.
1c-report-direct-query
Прямой запрос в отчётах 1С (СКД) без схемы компоновки.
1c-transactions-and-locks
Транзакции и управляемые блокировки: шаблон, порядок захвата.