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/orinks/accessiweather/hudnpx skills add Orinks/AccessiWeather --skill hudgit clone --depth 1 https://github.com/Orinks/AccessiWeatherWrote 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/orinks/accessiweather/hud)<a href="https://agentmods.dev/skills/orinks/accessiweather/hud"><img src="https://agentmods.dev/badge/skills/orinks/accessiweather/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.00018 | $0.00920 |
| Opus 5 | $0.00009 | $0.00460 |
| Sonnet 5 | $0.00004 | $0.00184 |
| Haiku 4.5 | $0.00002 | $0.00092 |
Grade B, and why
hud scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
1. **Layer 1 - Codex built-in statusLine**: Real-time TUI footer showing model, git branch, and context usage. Configured via `[tui] status_line` in `~/.codex/config.toml`. Zero code required. How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HUD Skill
The OMX HUD uses a two-layer architecture:
-
Layer 1 - Codex built-in statusLine: Real-time TUI footer showing model, git branch, and context usage. Configured via
[tui] status_linein~/.codex/config.toml. Zero code required. -
Layer 2 -
omx hudCLI command: Shows OMX-specific orchestration state (ralph, ultrawork, autopilot, team, pipeline, ecomode, turns). Reads.omx/state/files.
Quick Commands
| Command | Description |
|---|---|
omx hud |
Show current HUD (modes, turns, activity) |
omx hud --watch |
Live-updating display (polls every 1s) |
omx hud --json |
Raw state output for scripting |
omx hud --preset=minimal |
Minimal display |
omx hud --preset=focused |
Default display |
omx hud --preset=full |
All elements |
Presets
minimal
[OMX] ralph:3/10 | turns:42
focused (default)
[OMX] ralph:3/10 | ultrawork | team:3 workers | turns:42 | last:5s ago
full
[OMX] ralph:3/10 | ultrawork | autopilot:execution | team:3 workers | pipeline:exec | turns:42 | last:5s ago | total-turns:156
Setup
omx setup automatically configures both layers:
- Adds
[tui] status_lineto~/.codex/config.toml(Layer 1) - Writes
.omx/hud-config.jsonwith default preset (Layer 2) - Default preset is
focused; if HUD/statusline changes do not appear, restart Codex CLI once.
Layer 1: Codex Built-in StatusLine
Configured in ~/.codex/config.toml:
[tui]
status_line = ["model-with-reasoning", "git-branch", "context-remaining"]
Available built-in items (Codex CLI v0.101.0+):
model-name, model-with-reasoning, current-dir, project-root, git-branch, context-remaining, context-used, five-hour-limit, weekly-limit, codex-version, context-window-size, used-tokens, total-input-tokens, total-output-tokens, session-id
Layer 2: OMX Orchestration HUD
The omx hud command reads these state files:
.omx/state/ralph-state.json- Ralph loop iteration.omx/state/ultrawork-state.json- Ultrawork mode.omx/state/autopilot-state.json- Autopilot phase.omx/state/team-state.json- Team workers.omx/state/pipeline-state.json- Pipeline stage.omx/state/ecomode-state.json- Ecomode active.omx/state/hud-state.json- Last activity (from notify hook).omx/metrics.json- Turn counts
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 · 99 lines · 18 tokens per session scan B ed9b77c8e3bb
hud is a skill published in the GitHub repository Orinks/AccessiWeather (24 stars, last pushed 11d ago), licensed MIT. It adds 18 tokens to every session and 920 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.
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…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…