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/cwf818/creditgauge/installgit clone --depth 1 https://github.com/cwf818/creditgaugeWrote 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/cwf818/creditgauge/install)<a href="https://agentmods.dev/commands/cwf818/creditgauge/install"><img src="https://agentmods.dev/badge/commands/cwf818/creditgauge/install.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.00030 | $0.00385 |
| Opus 5 | $0.00015 | $0.00192 |
| Sonnet 5 | $0.00006 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
install 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 5d 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.
What it actually says
creditgauge :install
The wrapper writes the latest-cache-dir command into statusLine.command,
backs up any pre-existing statusLine to settings.json.bak.<ISO-timestamp>,
and preserves the original command in <claude-root>/plugins/creditgauge/state/upstream-cmd.sh
(sibling of config.json, stable across /plugin install rolls and cache
wipes) so it can be re-invoked as the upstream. Re-running on an
already-owned statusLine (the statusLine.command string still points to our
wrapper) is a no-op — the check uses isOurWrapperCommand(), not the
_creditgauge_managed marker (which is informational only).
Also seeds config.tokenPrices.json (sibling of config.json) if absent,
providing a global default price entry for the cost modules (m_tokenCost /
m_accTokenCost / m_sumTokenCost). Existing files are never overwritten.
The script runs locally with no network access and never prints
ANTHROPIC_AUTH_TOKEN.
Uninstalling: v0.9.x dropped the legacy --uninstall flag that
this command used to forward. Use the dedicated /creditgauge:uninstall
slash command (which calls scripts/uninstall.sh directly — the
source of truth).
Execute the install script with whatever arguments were passed to this command:
"${CLAUDE_PLUGIN_ROOT}/scripts/install.sh" $ARGUMENTS
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.
- 5d ago First seen · 35 lines · 30 tokens per session scan A 69045cbc7c34
install is a command published in the GitHub repository cwf818/creditgauge (2 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 385 once invoked, about $0.0002 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 commands, from other repositories
clean
Remove old .bak. backup files, keeping only the most recent per file.
uninstall
Uninstall creditgauge (CreditGauge), restore settings.json, and wipe the plugin's cache, marketplace, and loader rows.
clean-cache
Remove stale version directories under the plugin cache, keeping only the newest.
install
Install the creditgauge (CreditGauge) statusline wrapper into Claude Code's settings.json (for uninstall use the dedicated :uninstall slash command).
review
Run a Pi code review against local git state.
adversarial-review
Run a Pi review that challenges the implementation approach and design choices.