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 scalarian/oh-my-codex --skill plangit clone --depth 1 https://github.com/scalarian/oh-my-codexWrote 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/scalarian/oh-my-codex/plan)<a href="https://agentmods.dev/skills/scalarian/oh-my-codex/plan"><img src="https://agentmods.dev/badge/skills/scalarian/oh-my-codex/plan.svg" alt="Measured on agentmods" height="20"></a>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.00022 | $0.00486 |
| Opus 5 | $0.00011 | $0.00243 |
| Sonnet 5 | $0.00004 | $0.00097 |
| Haiku 4.5 | $0.00002 | $0.00049 |
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 7d 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
Purpose
Use $plan to create execution-ready slices. The output is not a strategy memo. It is the prompt-quality plan that downstream execution can follow without improvising core behavior.
Use When
- the work is bigger than a one-shot edit
- the request is clear enough to plan but not yet safe to execute
- verification, dependencies, or sequencing need to be locked in
Do Not Use When
- the task is still ambiguous enough for
$deep-interview - the change is a trivial single-file fix
- the user explicitly wants direct execution and the risk is low
Execution Policy
- Gather repo facts before asking the user about internals.
- Plans are prompts for execution, not prose for humans only.
- Every slice must fit in one focused context window.
- Every slice must have explicit verification.
- Prefer a small number of high-quality slices over a long TODO dump.
Plan Anatomy
Each slice should answer:
- what files are likely to change
- what the slice must do
- how to verify it
- what counts as done
- what it depends on
Workflow
- Read current intent artifacts:
.omx/plans/*-requirements.md.omx/plans/brownfield-map.md.omx/research/summary.md
- Derive the must-haves from the goal backward:
- what must be true when this is done?
- what artifacts and connections are required for those truths?
- Split the work into waves and slices:
- interface/contracts first
- implementation second
- verification/wiring last
- Write or refine:
- active phase plan
- verification map
- any required task queue items
- Keep every slice explicit about files, verification, and exit conditions.
Quality Bar
- no vague acceptance criteria
- no “make it work” tasks
- no giant slice that hides three subsystems
- no verify step that depends on hope
Deliverables
.omx/plans/<phase>.md.omx/plans/<phase>-verification.md- updated brownfield map or research summary when needed
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.
- 7d ago First seen · 73 lines · 22 tokens per session scan A 4575ebe81658
plan is a skill published in the GitHub repository scalarian/oh-my-codex (73 stars, last pushed 5mo ago), licensed MIT. It adds 22 tokens to every session and 486 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-30.
Other skills, from other repositories
printing-press-import
Bring a published CLI from the public library into the internal library so it's identical to a freshly-generated copy — module path reverted, manuscripts placed alongside, ready for /printing-press-polish or /printing-press-emboss. Use when the public library has a CLI you don't have locally, or to recover from a…
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
work
Execute an approved wish plan — orchestrate subagents per task group with fix loops, validation, and review handoff.
trace
Dispatch trace subagent to investigate unknown issues — reproduces, traces, and reports root cause for fix handoff.
preview-design
Render a real artifact through this branch's local MERIDIAN design code (not the published npm package) so the team can test the new Design Convention on the document / handoff / platform surfaces before it ships. Use for /preview-design, "preview the design convention", "render this with the new design", or Design…
sw-do
Implement a SpecWeave increment task by task through the ledger, with evidence per task and a verified close. Use for "implement this", "start working", "continue the increment", "keep going".