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 teamgit 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/team)<a href="https://agentmods.dev/skills/scalarian/oh-my-codex/team"><img src="https://agentmods.dev/badge/skills/scalarian/oh-my-codex/team.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.00026 | $0.00347 |
| Opus 5 | $0.00013 | $0.00173 |
| Sonnet 5 | $0.00005 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
omx-product-team 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 8d 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 Team
Purpose
Use this skill when the OMX plugin bundle is installed and the work needs durable orchestration rather than one-shot fanout. It is for queueing slices, assigning workers, collecting handoffs, and holding review state across sessions.
Use When
- the work splits cleanly into multiple slices
- workers need claims, leases, inbox messages, or review handoffs
- the runtime must survive longer than one local reasoning burst
Do Not Use When
- the task is serial and small
- there is no real slice boundary
- the review overhead would exceed the value of parallelism
Workflow
- Initialize runtime state with
omx team init. - Spawn or attach workers with
omx team spawn <workerId>. - Queue explicit slices with concrete outcomes.
- Claim tasks through worker ids, not ad-hoc ownership.
- Move finished work into review with a readable handoff note.
- Monitor health and drift:
omx team statusomx team inboxomx team logs <workerId>omx hud
- Resume or shut down intentionally with
omx team resumeoromx team shutdown.
Rules
- no silent completions
- no task goes straight from active to done without review
- no shutdown while live work is still in progress unless aborting
- if tmux is unavailable, treat degraded mode as a functional fallback, not proof of detached-worker behavior
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.
- 8d ago First seen · 44 lines · 26 tokens per session scan A bd86110dddc9
omx-product-team is a skill published in the GitHub repository scalarian/oh-my-codex (73 stars, last pushed 5mo ago), licensed MIT. It adds 26 tokens to every session and 347 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
dream
Batch-execute SHIP-ready wishes overnight — pick wishes, orchestrate workers, review PRs, wake up to results.
clickup
Use when managing ClickUp tasks, sprints, or comments via the cup CLI tool. Triggers: task queries, status updates, sprint tracking, creating subtasks, posting comments, threaded replies, standup summaries, searching tasks, checking overdue items, assigning tasks, listing spaces and lists, opening tasks in browser…
increment
Plan a unit of work as a SpecWeave increment - spec.md with Problem, Scope, numbered ACs and an Approach, plus tasks.md. Use when starting a feature, bug, hotfix or refactor.
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".
done
Close an increment: ledger check, specweave verify, optional review, then specweave complete. Use when all tasks are done and saying "close increment", "we are done", or "finish up".
handoff
Write a portable, secret-scrubbed handoff doc so this work can continue in any AI tool or on any machine. Use when saying "handoff", "running out of tokens", or "continue elsewhere".