A read-only procedure for exploring a codebase and writing a structured plan before implementation. The plan includes task dependencies and checks for deciding when the work is complete.

Use it to plan migrations, features, or fixes when you want a durable task list and acceptance criteria without implementing the changes.

It helps clarify where changes belong, what order to make them in, and what could go wrong before product code is edited.

plan — Skill by haoruilee

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 skills/haoruilee/oh-my-mcode/plan

Any agent

npx skills add haoruilee/oh-my-mcode --skill plan

Clone the repo

git clone --depth 1 https://github.com/haoruilee/oh-my-mcode

Made for: Claude Code, Codex.

Per session 110 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 675 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.

Model	Per session	Once invoked
Fable 5	$0.00110	$0.00675
Opus 5	$0.00055	$0.00338
Sonnet 5	$0.00022	$0.00135
Haiku 4.5	$0.00011	$0.00068

Measured 2d ago against content hash 8cfaaf2f3c04, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

skills/plan/SKILL.md · 56 lines

What it actually says

Plan Only

Read-only except run artifacts. Stop at PLAN_REVIEW. No product edits, no commits.

This skill does not register host /plan. Host /plan remains Plan Mode. We add a durable run + acceptance list; we do not replace Plan Mode.

中文名：仅规划。

Inputs

Goal and constraints.
Workspace root.
State tool: node <plugin-root>/scripts/run-store.mjs (see skills/max/references/run-store.md).
MCP first: if omm_run_create / omm_status / omm_inspect exist, use them instead of hand-writing run files. After plan, print mcode --session <id> and mcode --continue so the TUI can reopen the same host session.

Procedure

Create a run if none exists for this goal: create --goal "<goal>". If the user pointed at an existing run, load it (resume is for continuing execution — this skill still must not implement).
set-phase --phase DISCOVER. Load agents/explorer.md. Locate the module, tests, and risks. Diagnostic commands only.
set-phase --phase PLAN. Load agents/planner.md. Write plan.md (context, DAG, risks, rollback) and tasks.json (tasks + acceptance[]).
set-phase --phase PLAN_REVIEW. Present the plan. Ask whether to proceed with max mode. Do not start EXECUTE.

Output contract

plan.md and tasks.json on disk via the run store.
Acceptance criteria a verifier can run later without the planner present.
A clear stop: "Plan reviewed. Say max mode to execute, or edit the plan."

Failure handling

Missing tests / unknown verification path: still emit a plan, mark acceptance as kind: manual or name the missing command. Do not invent green tests.
User says "just do it": switch to the max skill; do not keep planning in a loop.

Examples

User: Make a plan only for migrating this module to Postgres

Discover the current store, list migration risks, write a DAG, stop.

User: max mode: migrate this module to Postgres

Wrong skill. That is the full loop (max).

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.

2d ago First seen · 56 lines · 110 tokens per session scan A 8cfaaf2f3c04

Subscribe to this mod's changes

plan is a skill published in the GitHub repository haoruilee/oh-my-mcode (51 stars, last pushed 4d ago), licensed MIT. It adds 110 tokens to every session and 675 once invoked, about $0.0006 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-30.

Code review Planning Writing and docs

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens