agentmods.dev

oh-my-engine: Command for Claude Code

.claude/commands/ome-plan.md

ome-plan is a command for Claude Code from oh-my-engine/oh-my-engine. It costs 13 tokens per session (758 once invoked), scanned A, original, MIT.

A planning workflow that turns a clarified coding task into implementation guidance, including interfaces, edge cases, and a test strategy.

In plain words
What is it for?
Use it when the goal is understood but the implementation still needs a precise plan, compatibility checks, or decisions about unusual cases.
Why use it?
It makes design decisions and the order of work explicit before code is changed, reducing avoidable rework.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions Claude Code.

This is oh-my-engine/oh-my-engine's own configuration. It tells Claude Code how to work on oh-my-engine itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything oh-my-engine configures →

not rated 5repo 2mo ago A scan 13 tokens original MIT
View source ↗ oh-my-engine/oh-my-engine
Reuse

Borrowing it

Nothing to install: this file belongs to oh-my-engine/oh-my-engine. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/oh-my-engine/oh-my-engine/main/.claude/commands/ome-plan.md
Clone the repo
git clone --depth 1 https://github.com/oh-my-engine/oh-my-engine

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.

agentmods badge for ome-plan

README.md
[![agentmods](https://agentmods.dev/badge/commands/oh-my-engine/oh-my-engine/ome-plan/github.svg)](https://agentmods.dev/commands/oh-my-engine/oh-my-engine/ome-plan)
Your own site
<a href="https://agentmods.dev/commands/oh-my-engine/oh-my-engine/ome-plan"><img src="https://agentmods.dev/badge/commands/oh-my-engine/oh-my-engine/ome-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.

agentmods 80×15 button for ome-plan

Your own site · 80×15
<a href="https://agentmods.dev/commands/oh-my-engine/oh-my-engine/ome-plan"><img src="https://agentmods.dev/badge/commands/oh-my-engine/oh-my-engine/ome-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 758 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00013 $0.00758
Opus 5.5 $0.00005 $0.00303
Sonnet 5.5 $0.00003 $0.00152
Haiku 4.5 $0.00001 $0.00076

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

Security

Grade A, and why

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

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.

.claude/commands/ome-plan.md · 97 lines

How it starts

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

ome-plan

Workflow Session Start (MANDATORY)

Before reading source files, planning, editing, or running verification for this workflow, you MUST start the OME workflow session by running:

ome plan $ARGUMENTS

This creates .ome/.session so the final ome finish command can record the execution into .ome/memory/executions/.

If a Windows PowerShell policy blocks the ome shim, run the same step through the cross-shell fallback: cmd.exe /c ome.cmd plan $ARGUMENTS. Do not hardcode this fallback on non-Windows platforms.

Claude Code fast path (other agents: ignore the leading ! and run the bare command via your shell tool):

!ome plan $ARGUMENTS

Purpose

Turn a clarified task into an implementation plan with interfaces, edge cases, and test strategy.

When to Use

  • Use when the goal is known but the implementation still needs design decisions.
  • Use when you need a precise sequence of edits before writing code.
  • Do not use when the task is already a tiny, obvious change.

Inputs

  • The clarified goal and scope.
  • Relevant project rules, source files, and existing patterns.
  • Known edge cases, compatibility constraints, and verification expectations.

Process

  1. Summarize the goal and any constraints that matter.
  2. Identify the narrowest implementation path that preserves existing behavior.
  3. List interfaces, files, or modules that may change.
  4. Call out edge cases and failure modes before coding.
  5. Define the test strategy and acceptance criteria.
  6. Produce a plan that another engineer could implement without guessing.
  7. Avoid writing code in the planning step.

Red Flags

  • The plan makes undocumented assumptions about public interfaces.
  • The approach requires broad refactors without a clear need.
  • Tests or edge cases are missing from the proposal.
  • The result is really implementation disguised as planning.

Common Rationalizations

  • "The obvious fix is good enough without a closer read of the rules."
  • "I can skip verification because the change is small."
  • "I should broaden the patch while I am here."
  • "A vague summary is enough for handoff."

Read the full file on GitHub · 97 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.

  1. 2mo ago First seen · 97 lines · 13 tokens per session scan A 4365d5d5e171

Subscribe to this mod's changes

ome-plan is a command published in the GitHub repository oh-my-engine/oh-my-engine (5 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 758 once invoked, about $0.0001 per session on Opus 5.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.

Planning
Related

ome-plan compared with commands from other repositories

ome-plan next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
ome-planoh-my-engine/oh-my-engineCommand52mo agoMITA13Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code