setup

A setup command for the Usage HUD, a status display that shows usage information in Claude Code. It configures the display, checks access credentials, and reports whether the required script exists.

In plain words
What is it for?
Use it to configure the Usage HUD in Claude Code, verify its OAuth token and script, and learn whether a restart is needed.
Why use it?
It helps install or repair the status display while preserving the existing status-line setting as a backup. It also identifies missing configuration, credentials, or files.

Command

Install

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.

agentmods
npx agentmods add commands/petercha90/cap/setup
Clone the repo
git clone --depth 1 https://github.com/PeterCha90/CAP
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 192 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00008 $0.00192
Opus 5 $0.00004 $0.00096
Sonnet 5 $0.00002 $0.00038
Haiku 4.5 $0.00001 $0.00019

Measured yesterday against content hash f6f8cb85ca78, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

setup 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 yesterday.

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. Read `~/.claude/settings.json` (or `$CLAUDE_CONFIG_DIR/settings.json`)
commands/setup.md · 24 lines

What it actually says

Setup Usage HUD

Instructions

  1. Read ~/.claude/settings.json (or $CLAUDE_CONFIG_DIR/settings.json)
  2. Check if statusLine.command contains usage-hud
  3. If not configured:
    • Back up existing statusLine to _statusLine_backup
    • Set statusLine to { "type": "command", "command": "node ${CLAUDE_PLUGIN_ROOT}/scripts/usage-hud.mjs" }
    • Save settings.json
  4. Verify OAuth token is accessible (macOS Keychain or credentials file)
  5. Report status and tell user to restart Claude Code if changes were made

Output

Report:

  • ✅ or ❌ statusLine configuration
  • ✅ or ❌ OAuth token found
  • ✅ or ❌ usage-hud.mjs exists at plugin path
Changes

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.

  1. yesterday First seen · 24 lines · 8 tokens per session scan B f6f8cb85ca78

Subscribe to this mod's changes

setup is a command published in the GitHub repository PeterCha90/CAP (10 stars, last pushed 3mo ago), licensed MIT. It adds 8 tokens to every session and 192 once invoked, about $0.0000 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-31.