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/reflection-basicgit clone --depth 1 https://github.com/alkoleft/mcp-bsl-platform-contextWhat 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.01232 |
| Opus 5 | $0.00000 | $0.00616 |
| Sonnet 5 | $0.00000 | $0.00246 |
| Haiku 4.5 | $0.00000 | $0.00123 |
Grade A, and why
reflection-basic 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 2d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- reflection-basic — 100% identical, 0 lines differ
- reflection-basic — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BASIC REFLECTION FOR LEVEL 2 TASKS
TL;DR: This document outlines a basic reflection approach for Level 2 (Simple Enhancement) tasks, ensuring that key insights and lessons are captured without unnecessary overhead.
🔍 REFLECTION OVERVIEW
Reflection is essential for improving future work, even for simpler Level 2 enhancements. This basic reflection approach focuses on key outcomes, challenges, and lessons learned while maintaining efficiency.
📋 REFLECTION PRINCIPLES
- Honesty: Accurately represent successes and challenges
- Specificity: Include concrete examples and observations
- Insight: Go beyond surface observations to derive useful insights
- Improvement: Focus on actionable takeaways for future work
- Efficiency: Keep reflection concise and focused on key learnings
📋 BASIC REFLECTION STRUCTURE
# Level 2 Enhancement Reflection: [Feature Name]
## Enhancement Summary
[Brief one-paragraph summary of the enhancement]
## What Went Well
- [Specific success point 1]
- [Specific success point 2]
- [Specific success point 3]
## Challenges Encountered
- [Specific challenge 1]
- [Specific challenge 2]
- [Specific challenge 3]
## Solutions Applied
- [Solution to challenge 1]
- [Solution to challenge 2]
- [Solution to challenge 3]
## Key Technical Insights
- [Technical insight 1]
- [Technical insight 2]
- [Technical insight 3]
## Process Insights
- [Process insight 1]
- [Process insight 2]
- [Process insight 3]
## Action Items for Future Work
- [Specific action item 1]
- [Specific action item 2]
- [Specific action item 3]
## Time Estimation Accuracy
- Estimated time: [X hours/days]
- Actual time: [Y hours/days]
- Variance: [Z%]
- Reason for variance: [Brief explanation]
📋 REFLECTION QUALITY
High-quality reflections for Level 2 tasks should:
- Provide specific examples rather than vague statements
- Identify concrete takeaways not general observations
- Connect challenges to solutions with clear reasoning
- Analyze estimation accuracy to improve future planning
- Generate actionable improvements for future work
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.
- 2d ago First seen · 178 lines · 1,232 tokens per session scan A d65b57dfe0d7
reflection-basic is a cursor rule published in the GitHub repository alkoleft/mcp-bsl-platform-context (190 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,232 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
archive-comprehensive
Cursor rule "archive-comprehensive" from alkoleft/platform-context-exporter, covering comprehensive archiving for level 4 tasks, 🔍 comprehensive archiving overview, 📋 archive template structure, 1. system overview and system overview.
reflection-comprehensive
Cursor rule "reflection-comprehensive" from alkoleft/platform-context-exporter, covering comprehensive reflection for level 4 tasks, 🔍 comprehensive reflection overview, 📋 reflection template structure, 1. system overview and system overview.
archive-basic
Cursor rule "archive-basic" from alkoleft/platform-context-exporter, covering basic archiving for level 2 tasks, 🔍 archiving overview, 📋 archiving principles, 📋 basic archive structure and enhancement archive: [feature name].
reflection-intermediate
The goal is to create a comprehensive memory-bank/reflection/reflection-[featureid].md document.
050-plan
When the user types /plan or asks to create a project plan, feature PRD, or retrospective.
session-memory
Use at conversation wrap-up or when the user explicitly indicates end-of-session — capture residual lessons not captured in-flight.