A command that turns a confirmed coding direction into a detailed implementation plan. The plan includes tasks, testing steps, review information, and a checklist that later execution can follow.

Use it to clarify requirements, research when needed, get confirmation, write a plan in the project, and mark that plan as active for later execution.

It prevents coding from starting before the goal and approach are understood and gives execution a clear contract.

plan — Command for Claude Code by KaimingWan/oh-my-kiro

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/KaimingWan/oh-my-kiro

agentmods

npx agentmods add commands/kaimingwan/oh-my-kiro/plan

Made for: Claude Code.

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

README.md

[![agentmods](https://agentmods.dev/badge/commands/kaimingwan/oh-my-kiro/plan/github.svg)](https://agentmods.dev/commands/kaimingwan/oh-my-kiro/plan)

Your own site

<a href="https://agentmods.dev/commands/kaimingwan/oh-my-kiro/plan"><img src="https://agentmods.dev/badge/commands/kaimingwan/oh-my-kiro/plan/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/kaimingwan/oh-my-kiro/plan"><img src="https://agentmods.dev/badge/commands/kaimingwan/oh-my-kiro/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 963 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00000	$0.00963
Opus 5.5	$0.00000	$0.00385
Sonnet 5.5	$0.00000	$0.00193
Haiku 4.5	$0.00000	$0.00096

Measured 2mo ago against content hash 4ef9f938f6ef, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

plan scanned grade A with 1 finding 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 2mo 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

2. **Each checklist item MUST include an inline verify command** using the format: `- [ ] Description | \`verify_command\`` (e.g., `- [ ] Gateway responds 200 | \`curl -sf http://127.0.0.1:8000/health\``). The verify com

commands/plan.md · 55 lines

How it starts

The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You MUST follow this exact sequence. Do NOT skip or reorder any step.

Step 1: Deep Understanding (skill: planning Phase 0)

Follow skills/omk-planning/SKILL.md Phase 0 to build deep understanding of the goal. Ask clarifying questions, research if needed, and present design for creative/architectural work. Do NOT proceed until the user confirms the direction. After user confirms: touch .brainstorm-confirmed

Step 2: Writing Plan (skill: planning)

Read skills/omk-planning/SKILL.md, then write a plan to docs/plans/-.md. The plan MUST include: Goal, Steps with TDD structure, an empty ## Review section, and a ## Checklist section with all acceptance criteria as - [ ] items. The checklist is the contract — @execute will not proceed without it.

Immediately after writing the plan file, update the active pointer so @execute can find it even from a different session:

echo "docs/plans/<plan-file>.md" > docs/plans/.active

Checklist Structure Rules (CRITICAL — Ralph Loop depends on these)

All checklist items go in the ## Checklist section (as defined in SKILL.md). Do NOT scatter - [ ] items inline across Phases — Ralph Loop and hooks parse ## Checklist as the single source of truth.
Each checklist item MUST include an inline verify command using the format: - [ ] Description | \verify_command`(e.g.,- [ ] Gateway responds 200 | `curl -sf http://127.0.0.1:8000/health\``). The verify command must return exit code 0 on success.
Checklist items must be actionable, not just observational. Bad: - [ ] System looks good. Good: - [ ] Config validated | \python3 -c "import json; json.load(open('config.json'))"``.
NEVER mark - [x] without running the verify command. Ralph Loop's revert_failed_checks() will revert items whose verify commands fail.

Step 3: Verify Checklist Exists

Before dispatching reviewer, confirm the plan file contains a ## Checklist section with at least one - [ ] item. If missing, add it NOW — do not proceed to review without it.

Read the full file on GitHub · 55 lines

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.

2mo ago First seen · 55 lines · 0 tokens per session scan A 4ef9f938f6ef

Subscribe to this mod's changes

plan is a command published in the GitHub repository KaimingWan/oh-my-kiro (107 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 963 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Planning

plan next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
planKaimingWan/oh-my-kiro	Command	107	7mo ago	MIT	A	0	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

plan