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.
git clone --depth 1 https://github.com/CynaCons/powerplanWrote 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/cynacons/powerplan/miniplan)<a href="https://agentmods.dev/rules/cynacons/powerplan/miniplan"><img src="https://agentmods.dev/badge/rules/cynacons/powerplan/miniplan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/cynacons/powerplan/miniplan"><img src="https://agentmods.dev/badge/rules/cynacons/powerplan/miniplan.svg" alt="Reviewed on agentmods" width="80" 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.00016 | $0.00153 |
| Opus 5.5 | $0.00006 | $0.00061 |
| Sonnet 5.5 | $0.00003 | $0.00031 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
miniplan 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 yesterday.
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.
What it actually says
End a multi-step turn with a miniplan: the current iteration seeded verbatim
from the powerplan MCP tool show_miniplan with checkboxes flipped, plus an
## Off-plan section for quick items this turn is tracking that are not in
PLAN.md (each marked → plan, → backlog or → drop). Print it in the chat;
never write it to a file. Then paste show_current_iteration verbatim in a code
block. Format: docs/MINIPLAN.md. PLAN.md changes only through powerplan tools.
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.
- yesterday First seen · 12 lines · 16 tokens per session scan A 2b974481cb9a
miniplan is a cursor rule published in the GitHub repository CynaCons/powerplan (0 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 153 once invoked, about $0.0001 per session on Opus 5.5. 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-10-30.
Other cursor rules, from other repositories
task-tracking-basic
Basic task tracking for Level 2 Simple Enhancement tasks.
notes
. ├── .cursor │ └── rules │ ├── DONE.mdc │ ├── WIP.mdc │ └── notes.mdc ├── reference │ ├── repomix-mcp-python-sdk.xml │ └── repomix-openai-agents-python-docs.xml ├── src │ └── agentsmcpserver │ ├── init.py │ ├── main.py │ ├── cli.py │ └── server.py ├── pyproject.toml └── README.md.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.