Claude HUD is a Claude Code plugin that displays information about the current coding-agent session, including context usage, active tools, running agents, and todo progress. It is used by Claude Code users who want session status visible while they work. The catalogue includes the plugin and related commands and instructions.
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.
git clone --depth 1 https://github.com/jarrodwatts/claude-hudWrote 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/commands/jarrodwatts/claude-hud/configure)<a href="https://agentmods.dev/commands/jarrodwatts/claude-hud/configure"><img src="https://agentmods.dev/badge/commands/jarrodwatts/claude-hud/configure/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/commands/jarrodwatts/claude-hud/configure"><img src="https://agentmods.dev/badge/commands/jarrodwatts/claude-hud/configure.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.00019 | $0.05429 |
| Opus 5 | $0.00010 | $0.02714 |
| Sonnet 5 | $0.00004 | $0.01086 |
| Haiku 4.5 | $0.00002 | $0.00543 |
Grade A, and why
configure 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- configure — 89% identical, 31 lines differ
How it starts
The opening of the file, as written. The whole thing — 474 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configure Claude HUD
FIRST: Resolve the active config directory ($CLAUDE_CONFIG_DIR when set, otherwise
~/.claude). Use the Read tool to load both of these files when they exist:
plugins/claude-hud/config.jsoninside the active config directory (the writable base).claude-hud.jsondirectly inside the active config directory (the manual override).
Store the base and override separately. The base file alone determines which flow to use. For current values and previews, compute the effective config by layering the override over the base with nested objects merged key by key and arrays/scalars replaced. Track every key defined by the override so the guided flow can identify settings that it cannot change.
Core Features (on by default)
These default to ON and are what most users keep. They ARE configurable
(display.showModel, display.showContextBar), but the guided flow keeps them
enabled — toggle them by editing config.json directly if needed:
- Model name
[Opus] - Context bar
████░░░░░░ 45%
Advanced settings such as colors.*, pathLevels, maxWidth, forceMaxWidth,
elementOrder, projectLineOrder, display.mergeGroups, display.timeFormat, display.contextValue,
display.modelFormat, display.modelOverride, display.modelSource, display.effortFormat, display.showProvider,
display.providerName, display.autocompactBuffer,
display.autoCompactWindow,
display.usageThreshold, display.sevenDayThreshold,
display.environmentThreshold, display.contextWarningThreshold,
display.contextCriticalThreshold, display.advisorOverride,
display.showAuth, display.showAuthUser, display.authUserLength, and the
display.externalUsage* keys, plus jjStatus.showDirty and
jjStatus.showConflicts, are preserved when saving but are not edited by this
guided flow.
Two Flows Based on Config State
Flow A: New User (no config)
Questions: Layout → Preset → Language → Turn Off → Turn On → Custom Line
Flow B: Update Config (config exists)
Questions: Turn Off → Turn On → Git Style → Layout/Reset → Language → Custom Line (6 questions max)
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 · 474 lines · 19 tokens per session scan A 4029fa1f351a
configure is a command published in the GitHub repository jarrodwatts/claude-hud (27,870 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 5,429 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 commands, from other repositories
atomic-plan
Write a design doc (concepts, business rules, approaches) and a checkpoint-table spec (contract) for non-trivial work; inline spec only for trivial. Gauges triviality; loops spec authoring with subagents. Human-facing artifact, Mermaid diagrams allowed.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
Stage, commit, and optionally ship further. Pass an escalation token (push, pr, merge, squash, squash merge) to skip the prompt. With no token, commits then asks how far to ship. Delegates message format to the atomic-git-discipline skill.
create-task-list.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
adopt-roadmap.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.