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/junghwayang/oh-my-codex/hudnpx skills add junghwaYang/oh-my-codex --skill hudgit clone --depth 1 https://github.com/junghwaYang/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/junghwayang/oh-my-codex/hud)<a href="https://agentmods.dev/skills/junghwayang/oh-my-codex/hud"><img src="https://agentmods.dev/badge/skills/junghwayang/oh-my-codex/hud.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 | $0.00000 | $0.00752 |
| Opus 5 | $0.00000 | $0.00376 |
| Sonnet 5 | $0.00000 | $0.00150 |
| Haiku 4.5 | $0.00000 | $0.00075 |
Grade A, and why
hud 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 5d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HUD Skill
Heads-Up Display for real-time orchestration metrics.
What It Shows
┌─────────────────────────────────────────────────────────────────┐
│ OMC │ Mode: autopilot │ Agents: 4 │ Tasks: 12/15 │ Tokens: 45K │
└─────────────────────────────────────────────────────────────────┘
Metrics Displayed
Mode
Current execution mode:
- autopilot
- ultrawork
- team
- eco
- plan
Agent Status
Active agents and their status:
- PM: coordinating
- Frontend: executing
- Backend: waiting
- Tester: idle
Task Progress
Tasks completed / total:
- 12/15 (80%)
- Current: "Implement user validation"
Token Usage
Tokens consumed:
- Current session: 45K
- Estimated remaining: ~20K
- Cost estimate: $0.15
Time
Elapsed time:
- Session: 15m 23s
- Current task: 2m 10s
Display Modes
Minimal (statusline)
OMC │ autopilot │ 4 agents │ 80% │ 45K tokens
Standard
┌─ Oh My Codex ─────────────────────────────────┐
│ Mode: autopilot Agents: 4 Progress: 80% │
│ Current: Implement user validation │
│ Tokens: 45K (~$0.15) Time: 15m 23s │
└───────────────────────────────────────────────┘
Detailed
╔═══════════════════════════════════════════════════════════════╗
║ OH MY CODEX HUD ║
╠═══════════════════════════════════════════════════════════════╣
║ Mode: autopilot ║
║ Session: 20260213_143022 ║
╠───────────────────────────────────────────────────────────────╣
║ AGENTS ║
║ PM │ coordinating │ tasks assigned: 15 ║
║ Frontend │ executing │ UserForm component ║
║ Backend │ waiting │ - ║
║ Tester │ idle │ - ║
╠───────────────────────────────────────────────────────────────╣
║ PROGRESS ║
║ [████████████░░░░] 12/15 tasks (80%) ║
║ Current: Implement user validation ║
╠───────────────────────────────────────────────────────────────╣
║ RESOURCES ║
║ Tokens: 45,234 (~$0.15) ║
║ Time: 15m 23s ║
║ Model: o3 (85%) | gpt-4.1-mini (15%) ║
╚═══════════════════════════════════════════════════════════════╝
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.
- 5d ago First seen · 127 lines · 0 tokens per session scan A 0b93a8bb1ba9
hud is a skill published in the GitHub repository junghwaYang/oh-my-codex (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 752 tokens. 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…