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-architecturegit 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-phase-architecture)<a href="https://agentmods.dev/rules/alkoleft/platform-context-exporter/creative-phase-architecture"><img src="https://agentmods.dev/badge/rules/alkoleft/platform-context-exporter/creative-phase-architecture.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 | $0.00000 | $0.01401 |
| Opus 5 | $0.00000 | $0.00700 |
| Sonnet 5 | $0.00000 | $0.00280 |
| Haiku 4.5 | $0.00000 | $0.00140 |
Grade A, and why
creative-phase-architecture 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 4d 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-architecture — 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: ARCHITECTURE DESIGN
TL;DR: This document provides structured guidance for architectural design decisions during creative phases, ensuring comprehensive evaluation of options and clear documentation of architectural choices.
🏗️ ARCHITECTURE DESIGN WORKFLOW
graph TD
Start["Architecture<br>Design Start"] --> Req["1. Requirements<br>Analysis"]
Req --> Comp["2. Component<br>Identification"]
Comp --> Options["3. Architecture<br>Options"]
Options --> Eval["4. Option<br>Evaluation"]
Eval --> Decision["5. Decision &<br>Documentation"]
Decision --> Valid["6. Validation &<br>Verification"]
style Start fill:#4da6ff,stroke:#0066cc,color:white
style Req fill:#ffa64d,stroke:#cc7a30,color:white
style Comp fill:#4dbb5f,stroke:#36873f,color:white
style Options fill:#d94dbb,stroke:#a3378a,color:white
style Eval fill:#4dbbbb,stroke:#368787,color:white
style Decision fill:#d971ff,stroke:#a33bc2,color:white
style Valid fill:#ff71c2,stroke:#c23b8a,color:white
📋 ARCHITECTURE DECISION TEMPLATE
# Architecture Decision Record
## Context
- System Requirements:
- [Requirement 1]
- [Requirement 2]
- Technical Constraints:
- [Constraint 1]
- [Constraint 2]
## Component Analysis
- Core Components:
- [Component 1]: [Purpose/Role]
- [Component 2]: [Purpose/Role]
- Interactions:
- [Interaction 1]
- [Interaction 2]
## Architecture Options
### Option 1: [Name]
- Description: [Brief description]
- Pros:
- [Pro 1]
- [Pro 2]
- Cons:
- [Con 1]
- [Con 2]
- Technical Fit: [High/Medium/Low]
- Complexity: [High/Medium/Low]
- Scalability: [High/Medium/Low]
### Option 2: [Name]
[Same structure as Option 1]
## Decision
- Chosen Option: [Option name]
- Rationale: [Explanation]
- Implementation Considerations:
- [Consideration 1]
- [Consideration 2]
## Validation
- Requirements Met:
- [✓] Requirement 1
- [✓] Requirement 2
- Technical Feasibility: [Assessment]
- Risk Assessment: [Evaluation]
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.
- 4d ago First seen · 187 lines · 0 tokens per session scan A edc168b675ad
creative-phase-architecture 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,401 tokens. A static security scan graded it A with 0 findings. It is 100% identical to creative-phase-architecture, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
1c-coding-standards
Стандарты кода BSL: именование, запросы, коллекции.
bsl-ssl
Переиспользование БСП, разметка правок типовых модулей, устаревшие объекты.
edt-form-xml-requirements
Требования EDT к XML-формам (Form.form): extInfo, дефолты полей.
1c-report-direct-query
Прямой запрос в отчётах 1С (СКД) без схемы компоновки.
1c-transactions-and-locks
Транзакции и управляемые блокировки: шаблон, порядок захвата.
async-methods-1c
Асинхронные методы 1С: Асинх/Ждать/Обещание (8.3.18+).