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/mcp-bsl-platform-context/architectural-planninggit clone --depth 1 https://github.com/alkoleft/mcp-bsl-platform-contextWrote 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/mcp-bsl-platform-context/architectural-planning)<a href="https://agentmods.dev/rules/alkoleft/mcp-bsl-platform-context/architectural-planning"><img src="https://agentmods.dev/badge/rules/alkoleft/mcp-bsl-platform-context/architectural-planning.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.06209 |
| Opus 5 | $0.00000 | $0.03104 |
| Sonnet 5 | $0.00000 | $0.01242 |
| Haiku 4.5 | $0.00000 | $0.00621 |
Grade A, and why
architectural-planning 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 6d 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 architectural-planning — 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 — 809 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ARCHITECTURAL PLANNING FOR LEVEL 4 TASKS
TL;DR: This document outlines a comprehensive architectural planning approach for Level 4 (Complex System) tasks, ensuring a robust, scalable, and maintainable architecture that aligns with business objectives and technical requirements.
🔍 ARCHITECTURAL PLANNING OVERVIEW
Level 4 Complex System tasks require thorough architectural planning to ensure the resulting system is robust, scalable, maintainable, and aligned with business objectives. This document outlines a structured approach to architectural planning that systematically addresses key concerns and produces comprehensive documentation.
flowchart TD
classDef phase fill:#f9d77e,stroke:#d9b95c,color:#000
classDef artifact fill:#f4b8c4,stroke:#d498a4,color:#000
classDef verification fill:#c5e8b7,stroke:#a5c897,color:#000
Start([Begin Architectural<br>Planning]) --> Reqs[Analyze<br>Requirements]
Reqs --> Context[Define Business<br>Context]
Context --> Vision[Establish Vision<br>and Goals]
Vision --> Principles[Define Architectural<br>Principles]
Principles --> Constraints[Identify<br>Constraints]
Constraints --> Explore[Explore<br>Alternatives]
Explore --> Evaluate[Evaluate<br>Options]
Evaluate --> Decision[Document<br>Decisions]
Decision --> Create[Create Architecture<br>Documentation]
Create --> Validate[Validate<br>Architecture]
Validate --> Communicate[Communicate<br>Architecture]
Communicate --> Verification{Architecture<br>Verification}
Verification -->|Pass| Complete([Architectural<br>Planning Complete])
Verification -->|Fail| Revise[Revise<br>Architecture]
Revise --> Verification
Reqs -.-> ReqDoc((Requirements<br>Document))
Context -.-> ConDoc((Context<br>Document))
Vision -.-> VisDoc((Vision<br>Document))
Principles -.-> PrinDoc((Principles<br>Document))
Explore -.-> AltDoc((Alternatives<br>Analysis))
Decision -.-> ADR((Architecture<br>Decision Records))
Create -.-> ArchDoc((Architecture<br>Documentation))
class Start,Complete milestone
class Reqs,Context,Vision,Principles,Constraints,Explore,Evaluate,Decision,Create,Validate,Communicate,Revise step
class Verification verification
class ReqDoc,ConDoc,VisDoc,PrinDoc,AltDoc,ADR,ArchDoc artifact
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.
- 6d ago First seen · 809 lines · 6,209 tokens per session scan A 28cc7d488d31
architectural-planning is a cursor rule published in the GitHub repository alkoleft/mcp-bsl-platform-context (191 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 6,209 tokens. A static security scan graded it A with 0 findings. It is 100% identical to architectural-planning, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
111-java-object-oriented-design
Java Object-Oriented Design Guidelines.
131-java-refactoring-with-modern-features
Modern Java Development Guidelines (Java 8+).
133-java-data-oriented-programming
Java rules to apply data oriented programming style.
113-java-general-guidelines
This document outlines general Java coding guidelines covering fundamental aspects such as naming conventions for packages, classes, methods, variables, and constants; code formatting rules including indentation, line length, brace style, and whitespace usage; standards for organizing import statements; best practices…
115-java-concurrency
Java rules for Concurrency objects.
122-java-integration-testing
Java Integration testing guidelines.