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 commands/mil-orb/claude-gauge/configgit clone --depth 1 https://github.com/mil-orb/claude-gaugeWrote 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/mil-orb/claude-gauge/config)<a href="https://agentmods.dev/commands/mil-orb/claude-gauge/config"><img src="https://agentmods.dev/badge/commands/mil-orb/claude-gauge/config.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.1 | $0.00009 | $0.00588 |
| Opus 5 | $0.00005 | $0.00294 |
| Sonnet 5 | $0.00002 | $0.00118 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade B, and why
config 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 6d 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.
- If you can't find the config, check `~/.claude/plugins/` and its subdirectories How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
claude-gauge Configuration
You are configuring the claude-gauge plugin. Read the current config, then walk the user through each setting interactively using AskUserQuestion.
Steps
-
Read current config from the plugin directory:
- Find the plugin root by checking
~/.claude/plugins/for claude-gauge, or use the path from~/.claude/settings.jsonstatusLine command - Read
config.jsonfrom that directory - Show the user their current settings in a brief summary
- Find the plugin root by checking
-
Walk through each setting using AskUserQuestion, one at a time. Show the current value and let them pick a new one or keep the current. Group into two questions:
Question 1 — Visual style (ask all three together):
display: bar (filling gauge, default), drain (emptying tank), dots (circle pips), blocks (braille), compact (text only). Default: barcolor: gradient (green→yellow→red), ocean (cyan→blue→purple), ember (yellow→orange→red), frost (white→blue), retro (CGA hard steps), spectrum (per-character gradient fill), mono (grayscale). Default: gradientbar_size: small (10), medium (20), large (30), xlarge (40), or a custom number. Default: medium
Question 2 — Info segments (ask toggles together):
show_cost: show running session cost in USD. Default: falseshow_duration: show elapsed session time. Default: trueshow_lines: show lines added/removed. Default: false
Question 3 — Currency (only ask if show_cost is enabled):
currency_rate: exchange rate from USD (e.g. 0.79 for GBP). Null means show USD. Symbol is auto-detected from locale.
-
Write the updated config.json to the plugin directory. Preserve the comment keys (lines starting with
//) for documentation. Format it nicely. -
Confirm the changes and remind the user that settings take effect on the next status line refresh — no restart needed.
Important
- The config file lives in the plugin installation directory, NOT the project source
- Typical path:
~/.claude/plugins/claude-gauge/config.jsonor check~/.claude/settings.jsonfor the statusLine command path - If you can't find the config, check
~/.claude/plugins/and its subdirectories - Do NOT modify any files other than config.json
- Use the Edit tool to update config.json, not Write, to preserve structure
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.
- 6d ago First seen · 42 lines · 9 tokens per session scan B c452ec84e429
config is a command published in the GitHub repository mil-orb/claude-gauge (5 stars, last pushed 5mo ago), licensed MIT. It adds 9 tokens to every session and 588 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.
Other commands, from other repositories
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database.
github-actions
Design, review, secure, and debug GitHub Actions workflows — reusable workflows, OIDC federation, SHA pinning, token scoping, promotion orchestration, and CI failure diagnosis.
fluxcd
FluxCD entry point — routes to the right workflow based on what you need. Live cluster issue → structured 5-workflow debug trace. Repo health check → 6-phase audit (discovery, validation, API compliance, best practices, security). Helm chart review → helmchart. Starts by asking one question to confirm the right mode.
genshijin-compress
Markdown・テキストファイルを原始人形式へ安全圧縮.
feat
Quick feature commit. Use for new feature, add feature, implement, create new.
nyann:diff-profile
Compare two nyann profiles side-by-side and show what changes between them: hooks, branching, CI, documentation, extras, governance. Useful before switching profiles to understand the impact.