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 instructions/sj817/claude-code-plugin-hud/claude-mdgit clone --depth 1 https://github.com/sj817/claude-code-plugin-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/instructions/sj817/claude-code-plugin-hud/claude-md)<a href="https://agentmods.dev/instructions/sj817/claude-code-plugin-hud/claude-md"><img src="https://agentmods.dev/badge/instructions/sj817/claude-code-plugin-hud/claude-md.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.01165 | $0.01165 |
| Opus 5 | $0.00583 | $0.00583 |
| Sonnet 5 | $0.00233 | $0.00233 |
| Haiku 4.5 | $0.00117 | $0.00117 |
Grade A, and why
claude-code-plugin-hud CLAUDE.md 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 4d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
claude-code-plugin-hud — project notes
A Rust CLI that renders the Claude Code statusline, shipped as a Claude Code plugin.
- Package name:
claude-code-plugin-hud - Binary name:
claude-hud(kept short) - Prebuilt per-platform binaries ship in
dist/. - The namespaced
/claude-code-plugin-hud:setupcommand wires a binary into the user'ssettings.json. Plugins cannot set the mainstatusLinethemselves; only a command can.
How the statusline contract works
- Claude Code streams session JSON to the binary on stdin. Whatever the binary prints to stdout is shown, one rendered row per printed line.
- It runs after each assistant message, after
/compact, and on permission/vim changes (debounced 300ms). It does not re-run while you type. - Terminal size comes from the
COLUMNS/LINESenv vars (v2.1.153+), nottput.COLUMNSis the whole terminal: Claude Code then insets the statusline bystatusLine.paddingcolumns per side, so the drawable width is narrower thanCOLUMNS. - Width math must count emoji as terminals paint them.
unicode-widthfollows East_Asian_Width, which calls⏱(U+23F1) one cell;char_cellsinrender.rsoverrides that range to 2. - Many JSON fields are optional or null (see
src/input.rs). Never unwrap. - Newer fields are also version-gated:
prompt_cacheandrate_limits.spend_limitneed v2.1.251+,pr.kindneeds v2.1.234+. Model them asOptionand keep a fallback, so older builds still render fully. - Permission mode (auto/plan/…) is not in the statusline JSON, so the HUD does
not show it. Hooks expose
permission_mode, but no hook fires on a bare shift+tab toggle, so it cannot be shown reliably. Omitted intentionally.
Architecture
| File | Responsibility |
|---|---|
src/main.rs |
Read stdin, parse, read $COLUMNS/$LINES, subtract the statusline padding, print. |
src/input.rs |
Serde structs; every field optional/defaulted. |
src/render.rs |
Layout rules: constant height, width-aware drop by priority, single bar, smart path. Start here for display changes. |
src/git.rs |
Branch + dirty flag, cached per session_id (5s TTL). |
src/theme.rs |
Calm 16-color palette, three accents (pink cache, soft-gold folder, orange quota band), and the usage / four-band quota threshold colors. |
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.
- 4d ago First seen · 88 lines · 1,165 tokens per session scan A 95501c7f2157
claude-code-plugin-hud CLAUDE.md is an instructions file published in the GitHub repository sj817/claude-code-plugin-hud (3 stars, last pushed 6d ago), licensed MIT. It adds 1,165 tokens to every session, about $0.0058 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-31.
Other instructions, from other repositories
cc-hud CLAUDE.md
Instructions for WaterTian/cc-hud, covering claude.md — cc-hud 项目指令, 项目概述, 技术栈, 项目结构 and 数据流.
cc-zhipu-hud CLAUDE.md
Instructions for beiyuii/cc-zhipu-hud, covering cc-zhipu-hud, tech stack, commands, project structure and data flow.
cc-zhipu-hud AGENTS.md
Instructions for beiyuii/cc-zhipu-hud, covering cc-zhipu-hud, tech stack, commands, project structure and key design decisions.
claude-hud-enhanced CLAUDE.md
Instructions for johnleeGitHub/claude-hud-enhanced, covering claude.md, project overview, build commands, test (node.js test runner — requires build first) and test (bun — runs source .ts directly, no build needed).
river-review GEMINI.md
Gemini CLI instructions for s977043/river-review, covering gemini instructions (river-review), 必須チェック, gemini-specific tips, prompt assembly and development tips.
living-manual CLAUDE.md
Instructions for dougstanford/living-manual, covering living-manual, start of every session, how work lands — non-negotiable, user's manual (living-manual) and releasing.