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.00943 |
| Opus 5.5 | $0.00008 | $0.00377 |
| Sonnet 5.5 | $0.00004 | $0.00189 |
| Haiku 4.5 | $0.00002 | $0.00094 |
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 28d 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, 495 lines differ
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configure Claude HUD
Read the current config
The config directory is $CLAUDE_CONFIG_DIR when set, otherwise ~/.claude. Read these files if they exist:
plugins/claude-hud/config.json: the base config. This command writes only this file.claude-hud.jsonin the config directory: a manual per-directory override. It uses the same shape and its values win. Never write or delete it.
The effective config is the base with the override layered on top: nested objects merge key by key, and arrays and scalars are replaced. Missing keys use the defaults in the README's configuration table. Use the effective values when describing the current state.
Ask
Ask these with AskUserQuestion, in two batches of up to four. Put the current value in each question. In multi-select questions, every listed item becomes true if selected and false if not.
Layout (single select)
- "Expanded":
lineLayout: "expanded",showSeparators: false - "Compact":
lineLayout: "compact",showSeparators: false - "Compact + separators":
lineLayout: "compact",showSeparators: true
Activity lines (multi-select)
- "Tools":
display.showTools - "Agents":
display.showAgents - "Todos":
display.showTodos - "Skills & MCP":
display.showSkills,display.showMcp
Session info (multi-select)
- "Cost":
display.showCost - "Duration":
display.showDuration - "Session name":
display.showSessionName - "Reasoning effort":
display.showEffortLevel
Usage limits (single select)
- "Bar (default)":
display.showUsage: true,display.usageBarEnabled: true,display.usageCompact: false - "Text":
display.showUsage: true,display.usageBarEnabled: false,display.usageCompact: false - "Compact":
display.showUsage: true,display.usageCompact: true - "Hidden":
display.showUsage: false
Git (single select)
- "Branch + dirty (default)":
gitStatus.enabled: true,showDirty: true,showAheadBehind: false,showFileStats: false - "Branch only":
gitStatus.enabled: true,showDirty: false,showAheadBehind: false,showFileStats: false - "Ahead/behind":
gitStatus.enabled: true,showDirty: true,showAheadBehind: true,showFileStats: false - "File stats":
gitStatus.enabled: true,showDirty: true,showAheadBehind: false,showFileStats: true
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.
- 28d ago Changed · -396 lines 732bcda73408
- 2mo ago First seen · 474 lines · 19 tokens per session scan A 4029fa1f351a
configure is a command published in the GitHub repository jarrodwatts/claude-hud (29,009 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 943 once invoked, about $0.0001 per session on Opus 5.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.
safe-build
Build the application for development or production.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.