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 skills add haoruilee/oh-my-mcode --skill plangit clone --depth 1 https://github.com/haoruilee/oh-my-mcodeWrote 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.
[](https://agentmods.dev/skills/haoruilee/oh-my-mcode/plan)<a href="https://agentmods.dev/skills/haoruilee/oh-my-mcode/plan"><img src="https://agentmods.dev/badge/skills/haoruilee/oh-my-mcode/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.
<a href="https://agentmods.dev/skills/haoruilee/oh-my-mcode/plan"><img src="https://agentmods.dev/badge/skills/haoruilee/oh-my-mcode/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00110 | $0.00675 |
| Opus 5.5 | $0.00044 | $0.00270 |
| Sonnet 5.5 | $0.00022 | $0.00135 |
| Haiku 4.5 | $0.00011 | $0.00068 |
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 1mo 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
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(seeskills/max/references/run-store.md). - MCP first: if
omm_run_create/omm_status/omm_inspectexist, use them instead of hand-writing run files. After plan, printmcode --session <id>andmcode --continueso 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 (resumeis for continuing execution — this skill still must not implement). set-phase --phase DISCOVER. Loadagents/explorer.md. Locate the module, tests, and risks. Diagnostic commands only.set-phase --phase PLAN. Loadagents/planner.md. Writeplan.md(context, DAG, risks, rollback) andtasks.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.mdandtasks.jsonon disk via the run store.- Acceptance criteria a verifier can run later without the planner present.
- A clear stop: "Plan reviewed. Say
max modeto execute, or edit the plan."
Failure handling
- Missing tests / unknown verification path: still emit a plan, mark acceptance as
kind: manualor name the missing command. Do not invent green tests. - User says "just do it": switch to the
maxskill; 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).
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.
- 1mo ago First seen · 56 lines · 110 tokens per session scan A 8cfaaf2f3c04
plan is a skill published in the GitHub repository haoruilee/oh-my-mcode (51 stars, last pushed 2mo ago), licensed MIT. It adds 110 tokens to every session and 675 once invoked, about $0.0004 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-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…