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 ultraworkgit 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/ultrawork)<a href="https://agentmods.dev/skills/scalarian/oh-my-codex/ultrawork"><img src="https://agentmods.dev/badge/skills/scalarian/oh-my-codex/ultrawork/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/scalarian/oh-my-codex/ultrawork"><img src="https://agentmods.dev/badge/skills/scalarian/oh-my-codex/ultrawork.svg" alt="Reviewed on agentmods" width="80" 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.00029 | $0.00349 |
| Opus 5 | $0.00015 | $0.00175 |
| Sonnet 5 | $0.00006 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
omx-product-ultrawork 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 9d 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
OMX Product Ultrawork
Purpose
Use this skill when the OMX plugin bundle is installed and you want the product-default operating mode. It is the packaged entrypoint for "figure out the right path, then finish the work."
Routing Rules
- vague or risky request -> clarify with
$deep-interview - clear but broad request -> build a real execution prompt with
$plan - one bounded slice -> run with
$executor - parallel durable work -> escalate to
$team - missing repo understanding -> use
$traceor$research
Workflow
- Start or resume the repo session with
omx session startoromx session resume. - Inspect live state with
omx hud. - Decide whether the request needs clarification, planning, direct execution, or team escalation.
- Refresh durable artifacts under
.omx/before changing code:- plans
- research
- tasks
- review state
- Execute through the smallest mode that can actually finish the job.
- End with explicit verification and a recorded verdict.
Rules
- do not jump into editing when the objective is still ambiguous
- do not escalate to team mode if direct execution is cheaper
- do not claim completion without tests, checks, or other evidence
- keep
.omx/state aligned with reality throughout the run
Final Check
- the next action is explicit
- the chosen mode matches the task size
- verification exists
- runtime state is not lying about progress
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.
- 9d ago First seen · 46 lines · 29 tokens per session scan A 3617f409e80a
omx-product-ultrawork is a skill published in the GitHub repository scalarian/oh-my-codex (73 stars, last pushed 5mo ago), licensed MIT. It adds 29 tokens to every session and 349 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".