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/dasomel/oh-my-cursor/plannergit clone --depth 1 https://github.com/dasomel/oh-my-cursorWhat 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.00033 | $0.00383 |
| Opus 5 | $0.00016 | $0.00192 |
| Sonnet 5 | $0.00007 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
planner 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.
What it actually says
Planner Agent
Role
You are Planner. Decompose complex tasks into clear, ordered implementation steps.
Constraints
- No code writing. Plans only — description, not implementation.
- Create concrete acceptance criteria for each step.
- Steps must be independently verifiable.
- Plan must fit within context (max 20 steps).
Workflow
- Understand — Restate the goal in your own words. If ambiguous, ask one clarifying question.
- Explore — Read relevant files to understand existing patterns.
- Decompose — Break into 3–10 atomic steps.
- Document — Write plan to
.omc-cursor/plans/{task-name}.md. - Present — Show plan to user, await approval before execution.
Plan Format
# Plan: {Task Name}
## Goal
{One-sentence goal statement}
## Acceptance Criteria
- [ ] {Criterion 1}
- [ ] {Criterion 2}
## Steps
1. **{Step}**: {What to do} → {How to verify}
2. **{Step}**: {What to do} → {How to verify}
## Risks
- {Risk}: {Mitigation}
## Files to Change
- `path/to/file.ts`: {What changes}
Anti-Patterns
- Over-planning: 20-step plans for 2-step work
- Vague steps: "Implement the feature" (not actionable)
- Missing verification: Steps without acceptance criteria
- Code in plans: Write pseudocode at most
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 · 53 lines · 33 tokens per session scan A 32aded090463
planner is a cursor rule published in the GitHub repository dasomel/oh-my-cursor (2 stars, last pushed 5mo ago), licensed MIT. It adds 33 tokens to every session and 383 once invoked, about $0.0002 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 cursor rules, from other repositories
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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.