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 skills add jabrena/cursor-rules-examples --skill 020-planning-enhance-ai-plan-modegit clone --depth 1 https://github.com/jabrena/cursor-rules-examplesWrote 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/skills/jabrena/cursor-rules-examples/020-planning-enhance-ai-plan-mode)<a href="https://agentmods.dev/skills/jabrena/cursor-rules-examples/020-planning-enhance-ai-plan-mode"><img src="https://agentmods.dev/badge/skills/jabrena/cursor-rules-examples/020-planning-enhance-ai-plan-mode/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/skills/jabrena/cursor-rules-examples/020-planning-enhance-ai-plan-mode"><img src="https://agentmods.dev/badge/skills/jabrena/cursor-rules-examples/020-planning-enhance-ai-plan-mode.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.00074 | $0.00479 |
| Opus 5 | $0.00037 | $0.00239 |
| Sonnet 5 | $0.00015 | $0.00096 |
| Haiku 4.5 | $0.00007 | $0.00048 |
Grade A, and why
020-planning-enhance-ai-plan-mode 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 12d 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.
What it actually says
Java Design Plan Creation for Cursor Plan Mode
Guide the process of creating a structured plan using Cursor Plan mode. This is an interactive SKILL. Plans follow a consistent section structure suitable for Java feature implementation, refactoring, or API design.
What is covered in this Skill?
- Plan mode workflow: enter Plan mode, gather context, draft plan, iterate
- YAML frontmatter: name, overview, todos, isProject
- Required sections: Requirements Summary, Approach (with Mermaid), Task List, Execution Instructions, File Checklist, Notes
- London Style (outside-in) TDD pattern
- Plan execution discipline: update Status after each task before advancing
- Plan file path: .cursor/plans/YYYY-MM-DD_<name>.plan.md
Constraints
Gather context before drafting. Include Execution Instructions in every plan. Never advance to next task without updating the plan's Status column.
- MANDATORY: Run
datebefore starting to get date prefix for plan filename - MUST: Read the reference template fresh—do not use cached content
- MUST: Ask one or two questions at a time; never all at once
- MUST: Validate summary ("Does this capture what you need?") before proposing plan creation
- MUST: Wait for user to confirm "proceed" before generating the plan
- MUST: Include Execution Instructions section in every generated plan
When to use this skill
- Create a plan with Cursor Plan mode
- Write a plan with Claude Plan mode
Reference
For detailed guidance, examples, and constraints, see references/020-planning-enhance-ai-plan-mode.md.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 41 lines · 74 tokens per session scan A 47963d76c0f4
020-planning-enhance-ai-plan-mode is a skill published in the GitHub repository jabrena/cursor-rules-examples (2 stars, last pushed 16d ago), licensed Apache-2.0. It adds 74 tokens to every session and 479 once invoked, about $0.0004 per session on Opus 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-08-31.
Other skills, from other repositories
validate-architecture
Run boundary and structure validators against a Hydrogen storefront project. Reports cross-module imports, reverse imports from shared layers, dumping-ground folders, barrel files, forbidden Remix imports, and missing/duplicated route manifests.
testing
TDD, mocks, gauntlet, regression naming. Use when writing or expanding tests, not because testing.mdc is on. Produces the verifying test or manual check for this change; does not authorize unrelated refactors.
debugging
Evidence-first debug for unknown or intermittent bugs. Use when the cause is unknown or the user asks to diagnose. Establishes evidence and distinguishes confirmed causes from hypotheses. Diagnosis alone does not authorize implementation changes.
redesign-existing-projects
Audit then fix generic or AI-looking sites in place. Product apps apply findings through premium-ui-craft.
writing-pr
Use when writing or editing a pull request title or body.
debugging-loop
Systematic reproduce-isolate-fix-verify loop for bugs, test failures, and unexpected behavior. Use when something is broken and the cause is not yet known.