agentmods.dev

status

status is a command for Claude Code from PeterCha90/CAP. It costs 7 tokens per session (144 once invoked), scanned B, original, MIT.

A diagnostic command for the Usage HUD, a Claude Code status display that tracks usage information. It checks configuration, credentials, cached usage values, and available updates.

In plain words
What is it for?
Use it to inspect the status-line setup, verify the Usage HUD script and OAuth token, review cached five-hour and seven-day usage, and check for updates.
Why use it?
It collects the relevant checks in one compact report, making it easier to find why the display is not working or whether its data is outdated.

Command for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_DATA} variable. Also seen: reads .claude/ paths.

Part of the cap plugin — 1 skill, 3 commands, 1 hook shipped together

not rated 10repo 5mo ago B scan 7 tokens original MIT

Good fit Use it to inspect the status-line setup, verify the Usage HUD script and OAuth token, review cached five-hour and seven-day usage, and check for updates.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/petercha90/cap/status
View source ↗ PeterCha90/CAP
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.

Clone the repo
git clone --depth 1 https://github.com/PeterCha90/CAP

Made for: Claude Code.

Or install cap, the plugin that ships this one along with the rest of its 1 skill, 3 commands, 1 hook.

Wrote 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.

agentmods badge for status

README.md
[![agentmods](https://agentmods.dev/badge/commands/petercha90/cap/status/github.svg)](https://agentmods.dev/commands/petercha90/cap/status)
Your own site
<a href="https://agentmods.dev/commands/petercha90/cap/status"><img src="https://agentmods.dev/badge/commands/petercha90/cap/status/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.

agentmods 80×15 button for status

Your own site · 80×15
<a href="https://agentmods.dev/commands/petercha90/cap/status"><img src="https://agentmods.dev/badge/commands/petercha90/cap/status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 144 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00007 $0.00144
Opus 5.5 $0.00003 $0.00058
Sonnet 5.5 $0.00001 $0.00029
Haiku 4.5 $0.00001 $0.00014

Measured 1mo ago against content hash 5799d0e140bb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

status 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 1mo 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` and check `statusLine` configuration
commands/status.md · 20 lines

What it actually says

Usage HUD Status

Instructions

  1. Read ~/.claude/settings.json and check statusLine configuration
  2. Check if usage-hud.mjs exists at the plugin root
  3. Check OAuth token availability
  4. Read .usage-cache.json from ${CLAUDE_PLUGIN_DATA} and show:
    • Last fetch time
    • Cached 5h/7d utilization values
    • Cache age (fresh/stale)
  5. Read .update-cache.json and show:
    • Current version vs latest version
    • Update available: yes/no
  6. Print a compact diagnostic summary
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. 1mo ago First seen · 20 lines · 7 tokens per session scan B 5799d0e140bb

Subscribe to this mod's changes

status is a command published in the GitHub repository PeterCha90/CAP (10 stars, last pushed 5mo ago), licensed MIT. It adds 7 tokens to every session and 144 once invoked, about $0.0000 per session on Opus 5.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.

Analytics and metricsClaude Codepluginstatusline
Related

Other commands, from other repositories

configure

Configure HUD display options (layout, language, presets, display elements) while preserving advanced manual overrides.

jarrodwatts/claude-hud · 19 tokens

land

Resolve and squash merge one named, currently authorized pull request.

gmickel/flow-next · 13 tokens

analyze-context

USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.

RohiRIK/OpenLtm · 39 tokens

incident

Live incident response — intake a Sentry issue, stack trace, or symptom; gate mitigate-first vs root-cause-first; keep a UTC timeline. Use when production is broken RIGHT NOW; for the after-action write-up alone, use /orc:postmortem.

HigorAlves/orc · 54 tokens

me-cfd-review

Review thermal-fluid CFD setup, boundary conditions, mesh, wall treatment, convergence, validation, and whether the claims are supported.

hanhuark/mechanical-engineering-research-skill · 25 tokens

me-figure-discussion

Write or review thermal-fluid figure discussion with observation, physical mechanism, comparison, uncertainty, and claim limits.

hanhuark/mechanical-engineering-research-skill · 21 tokens