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/planning-comprehensivegit 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/planning-comprehensive)<a href="https://agentmods.dev/rules/alkoleft/mcp-bsl-platform-context/planning-comprehensive"><img src="https://agentmods.dev/badge/rules/alkoleft/mcp-bsl-platform-context/planning-comprehensive.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.01511 |
| Opus 5 | $0.00000 | $0.00756 |
| Sonnet 5 | $0.00000 | $0.00302 |
| Haiku 4.5 | $0.00000 | $0.00151 |
Grade A, and why
planning-comprehensive 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 5d 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 planning-comprehensive — 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LEVEL 3 COMPREHENSIVE PLANNING
TL;DR: This document provides structured planning guidelines for Level 3 (Intermediate Feature) tasks, focusing on comprehensive planning with creative phases and clear implementation strategies.
🏗️ PLANNING WORKFLOW
graph TD
Start["Planning Start"] --> Req["📋 Requirements<br>Analysis"]
Req --> Comp["🔍 Component<br>Analysis"]
Comp --> Design["🎨 Design<br>Decisions"]
Design --> Impl["⚙️ Implementation<br>Strategy"]
Impl --> Test["🧪 Testing<br>Strategy"]
Test --> Doc["📚 Documentation<br>Plan"]
Design --> Creative["Creative Phases:"]
Creative --> UI["UI/UX Design"]
Creative --> Arch["Architecture"]
Creative --> Algo["Algorithm"]
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 Design fill:#d94dbb,stroke:#a3378a,color:white
style Impl fill:#4dbbbb,stroke:#368787,color:white
style Test fill:#d971ff,stroke:#a33bc2,color:white
style Doc fill:#ff71c2,stroke:#c23b8a,color:white
🔄 LEVEL TRANSITION HANDLING
graph TD
L3["Level 3 Task"] --> Assess["Continuous<br>Assessment"]
Assess --> Down["Downgrade to<br>Level 1/2"]
Assess --> Up["Upgrade to<br>Level 4"]
Down --> L12Trigger["Triggers:<br>- Simpler than expected<br>- Limited scope<br>- Few components"]
Up --> L4Trigger["Triggers:<br>- System-wide impact<br>- Architectural changes<br>- High complexity"]
L12Trigger --> L12Switch["Switch to<br>Level 1/2 Workflow"]
L4Trigger --> L4Switch["Switch to<br>Level 4 Workflow"]
📋 PLANNING TEMPLATE
# Feature Planning Document
## Requirements Analysis
- Core Requirements:
- [ ] Requirement 1
- [ ] Requirement 2
- Technical Constraints:
- [ ] Constraint 1
- [ ] Constraint 2
## Component Analysis
- Affected Components:
- Component 1
- Changes needed:
- Dependencies:
- Component 2
- Changes needed:
- Dependencies:
## Design Decisions
- Architecture:
- [ ] Decision 1
- [ ] Decision 2
- UI/UX:
- [ ] Design 1
- [ ] Design 2
- Algorithms:
- [ ] Algorithm 1
- [ ] Algorithm 2
## Implementation Strategy
1. Phase 1:
- [ ] Task 1
- [ ] Task 2
2. Phase 2:
- [ ] Task 3
- [ ] Task 4
## Testing Strategy
- Unit Tests:
- [ ] Test 1
- [ ] Test 2
- Integration Tests:
- [ ] Test 3
- [ ] Test 4
## Documentation Plan
- [ ] API Documentation
- [ ] User Guide Updates
- [ ] Architecture Documentation
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.
- 5d ago First seen · 188 lines · 0 tokens per session scan A c7aef3cc95e8
planning-comprehensive 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 1,511 tokens. A static security scan graded it A with 0 findings. It is 100% identical to planning-comprehensive, 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+).
115-java-concurrency
Java rules for Concurrency objects.
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…
122-java-integration-testing
Java Integration testing guidelines.