Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add apappas1129/claude-skill-hud/plugin install claude-skill-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/skills/apappas1129/claude-skill-hud/skill-hud-setup)<a href="https://agentmods.dev/skills/apappas1129/claude-skill-hud/skill-hud-setup"><img src="https://agentmods.dev/badge/skills/apappas1129/claude-skill-hud/skill-hud-setup/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/skills/apappas1129/claude-skill-hud/skill-hud-setup"><img src="https://agentmods.dev/badge/skills/apappas1129/claude-skill-hud/skill-hud-setup.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.00046 | $0.00707 |
| Opus 5 | $0.00023 | $0.00353 |
| Sonnet 5 | $0.00009 | $0.00141 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade B, and why
skill-hud-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 10d 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. Read `~/.claude/settings.json`. If it doesn't exist, treat it as `{}`. How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill HUD setup
The claude-skill-hud plugin's hooks (which log skill invocations) are
already active now that the plugin is installed. The one piece a plugin
cannot wire up automatically is the main session status line — that's a
plain user-level settings.json field, not a plugin-managed component, so it
needs to be written once, explicitly.
This skill's job: add that one statusLine entry, without touching anything
else already in the user's settings.
Resolved paths for this install
These paths were substituted into this skill's content when it loaded, so they're already correct for wherever this plugin is installed on this machine:
- Plugin root:
${CLAUDE_PLUGIN_ROOT} - Persistent data directory:
${CLAUDE_PLUGIN_DATA} - Status line script:
${CLAUDE_PLUGIN_ROOT}/scripts/statusline.sh
Steps
-
Read
~/.claude/settings.json. If it doesn't exist, treat it as{}. -
Check the existing
statusLinekey, if any:- If it's already set to a command containing
scripts/statusline.shfrom this plugin's root, the HUD is already configured — tell the user this and stop, no changes needed. - If a different
statusLineis already configured (the user has their own custom one), stop and ask the user how they want to proceed. Do not silently overwrite it. Options: replace it, or skip HUD setup and let the user merge it manually. - If no
statusLinekey exists, proceed to step 3.
- If it's already set to a command containing
-
Add this exact block to the settings JSON, merging it in alongside any other existing top-level keys (do not remove or reorder unrelated keys):
"statusLine": { "type": "command", "command": "CLAUDE_PLUGIN_DATA=\"${CLAUDE_PLUGIN_DATA}\" \"${CLAUDE_PLUGIN_ROOT}/scripts/statusline.sh\"", "refreshInterval": 2 }The
CLAUDE_PLUGIN_DATA=...prefix is required: the main status line runs outside the plugin hook/MCP substitution system, so this is the one place that env var has to be set explicitly rather than relying on automatic injection.refreshIntervalis a safety net on top of the normal event-driven refresh (after each assistant message) — it forces a re-render every 2 seconds so the HUD can't visibly linger stale.
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.
- 10d ago First seen · 68 lines · 46 tokens per session scan B 9a291243104a
skill-hud-setup is a skill published in the GitHub repository apappas1129/claude-skill-hud (2 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 707 once invoked, about $0.0002 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.
Other skills, from other repositories
resolve-plugins
Curate Claude Code skill / MCP / hook picks against live upstream sources and pin them in .claude/settings.json. Adding a process harness (a paired skill set) is an ordinary pick this door handles. Reads stack from docs/techstack.md, workflow signal from docs/overview.md + existing pins, then live-queries six source…
journey-simulation
Use when caller wants to observe how a stranger encounters a flow, artifact, or sandbox — triggers like "simulate a user journey", "test our onboarding / checkout / signup", "will my ICP convert", "how does a cold reader experience this README", "first-time user test", "cognitive walkthrough", or any request to…
check-docs-consistency
Cross-reference project docs for drift, stale references, and contradictions. Outputs timestamped report. Discovers Markdown wherever it lives in the repo.
super-bootstrap
Public entry for the super-bootstrap pipeline — thin orchestrator. Git-inits if absent, then dispatches /super-bootstrap:harness-bootstrap to install or sync the generic runway (always; the runway self-detects fresh-vs-sync). Checks whether seed docs are substantive: greenfield seeds three GAP cards (overview…
release
Prepare a version release — bump version files, commit, and tag. Just run /release with no arguments.
merge
Absorb one or more feature branches into the base branch. Recommends merge vs rebase per branch. On conflict, aborts that branch + surfaces the file list + stops. Resolution out of scope; routes to the harness-named conflict-resolution agent or the user.