plan-execute

A rule set for planning coding tasks before implementation when they involve several steps, files, or architectural decisions.

In plain words
What is it for?
It helps create a written plan, break work into ordered steps, verify each change, and optionally review the completed implementation.
Why use it?
It makes the intended work and acceptance checks explicit, while requiring approval before execution.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/dasomel/oh-my-cursor/plan-execute
Clone the repo
git clone --depth 1 https://github.com/dasomel/oh-my-cursor
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 310 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00024 $0.00310
Opus 5 $0.00012 $0.00155
Sonnet 5 $0.00005 $0.00062
Haiku 4.5 $0.00002 $0.00031

Measured yesterday against content hash 433a246ea82b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

plan-execute 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.

rules/workflows/plan-execute.mdc · 55 lines

What it actually says

Plan-Execute Workflow

When to Use

  • Task requires 3+ steps
  • Changes touch multiple files
  • Architectural decisions involved
  • User says "plan then do", "plan first"

Steps

Step 1: Plan (Planner Role)

[Switching to Planner role]

1. Read relevant files to understand context
2. Decompose into atomic steps
3. Write to .omc-cursor/plans/{task}.md:
   - Goal
   - Acceptance criteria
   - Ordered steps with verification
   - Files to change
4. Present plan to user
5. STOP — await explicit approval

Step 2: Execute (Executor Role)

[Awaiting approval...]
[User approved — Switching to Executor role]

For each step:
1. Implement change
2. Run verification (test/build/lint)
3. Show actual output
4. Proceed to next step only on success

Step 3: Verify (Reviewer Role, optional)

[Switching to Reviewer role]
Review changes for quality and correctness

Approval Gate

NEVER proceed to execution without user approval of the plan.

If the task is time-sensitive and user says "just do it", skip the approval gate but still create the plan file for documentation.

Changes

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.

  1. yesterday First seen · 55 lines · 24 tokens per session scan A 433a246ea82b

Subscribe to this mod's changes

plan-execute is a cursor rule published in the GitHub repository dasomel/oh-my-cursor (2 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 310 once invoked, about $0.0001 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.