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 agentmods add skills/tobyilee/ccmonitor/omc-referencenpx skills add tobyilee/ccmonitor --skill omc-referencegit clone --depth 1 https://github.com/tobyilee/ccmonitorWhat 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 | $0.00048 | $0.01431 |
| Opus 5 | $0.00024 | $0.00715 |
| Sonnet 5 | $0.00010 | $0.00286 |
| Haiku 4.5 | $0.00005 | $0.00143 |
Grade A, and why
omc-reference 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OMC Reference
Use this built-in reference when you need detailed OMC catalog information that does not need to live in every CLAUDE.md session.
Agent Catalog
Prefix: oh-my-claudecode:. See agents/*.md for full prompts.
explore(haiku) — fast codebase search and mappinganalyst(opus) — requirements clarity and hidden constraintsplanner(opus) — sequencing and execution plansarchitect(opus) — system design, boundaries, and long-horizon tradeoffsdebugger(sonnet) — root-cause analysis and failure diagnosisexecutor(sonnet) — implementation and refactoringverifier(sonnet) — completion evidence and validationtracer(sonnet) — trace gathering and evidence capturesecurity-reviewer(sonnet) — trust boundaries and vulnerabilitiescode-reviewer(opus) — comprehensive code reviewtest-engineer(sonnet) — testing strategy and regression coveragedesigner(sonnet) — UX and interaction designwriter(haiku) — documentation and concise content workqa-tester(sonnet) — runtime/manual validationscientist(sonnet) — data analysis and statistical reasoningdocument-specialist(sonnet) — SDK/API/framework documentation lookupgit-master(sonnet) — commit strategy and history hygienecode-simplifier(opus) — behavior-preserving simplificationcritic(opus) — plan/design challenge and review
Model Routing
haiku— quick lookups, lightweight inspection, narrow docs worksonnet— standard implementation, debugging, and reviewopus— architecture, deep analysis, consensus planning, and high-risk review
Tools Reference
External AI / orchestration
/team N:executor "task"omc team N:codex|gemini "..."omc ask <claude|codex|gemini>/ccg
OMC state
state_read,state_write,state_clear,state_list_active,state_get_status
Team runtime
TeamCreate,TeamDelete,SendMessage,TaskCreate,TaskList,TaskGet,TaskUpdate
Notepad
notepad_read,notepad_write_priority,notepad_write_working,notepad_write_manual
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.
- 2d ago First seen · 142 lines · 48 tokens per session scan A c2cc27e1984f
omc-reference is a skill published in the GitHub repository tobyilee/ccmonitor (54 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 1,431 once invoked, about $0.0002 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
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…