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/topgauge/uninstallgit clone --depth 1 https://github.com/cwf818/topgaugeWrote 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/topgauge/uninstall)<a href="https://agentmods.dev/commands/cwf818/topgauge/uninstall"><img src="https://agentmods.dev/badge/commands/cwf818/topgauge/uninstall.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.00025 | $0.00577 |
| Opus 5 | $0.00013 | $0.00289 |
| Sonnet 5 | $0.00005 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
uninstall 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- uninstall — 92% identical, 34 lines differ
What it actually says
creditgauge :uninstall
Restores the original statusLine.command from the stable
plugins/creditgauge/state/upstream-cmd.txt (sibling of
config.json) if available, otherwise falls back to the most recent
pre-managed settings.json.bak.<ts>. Strips creditgauge@creditgauge
from enabledPlugins and extraKnownMarketplaces, wipes
cache/creditgauge/, the marketplace dir, and the plugin's row from
installed_plugins.json and known_marketplaces.json. Backs up
settings.json and the two JSON files with .<name>.bak.<timestamp>
before any destructive change. Runs scripts/clean.sh as its final step
to trim old backups (keeps only the most recent per file; user-named
backups like settings.json.bak-pre-v0.1.8 are not touched). Idempotent
— re-running on a clean system prints "nothing to do" and exits 0.
Default behavior (no flags) is a partial-preserve uninstall: the
state/ cache noise (cache.json / cache.stat.json /
upstream-cmd.sh / upstream-cmd.txt / per-project state.json) is
wiped, but your config.json, query_plugins/ overrides, and the
per-project <sessionId>.jsonl token-sample history are preserved on
disk and listed in a post-uninstall hint so you can decide whether to
keep them or delete them manually.
--completely does a full uninstall: in addition to the cache
noise, it also nukes config.json, query_plugins/, and the .jsonl
history — equivalent to a fresh install afterwards. Use this when you
want to start from a clean slate.
The env block of settings.json is never touched (your
ANTHROPIC_AUTH_TOKEN and other env vars are preserved).
Execute the uninstall script with whatever arguments were passed to this command:
"${CLAUDE_PLUGIN_ROOT}/scripts/uninstall.sh" $ARGUMENTS
After uninstall, re-install with:
/plugin marketplace add cwf818/creditgauge
/plugin install creditgauge@creditgauge
/reload-plugins
/creditgauge:install
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 · 52 lines · 25 tokens per session scan A d8e384cd4356
uninstall is a command published in the GitHub repository cwf818/topgauge (2 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 577 once invoked, about $0.0001 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.
reset
Wipe the 3 cache files for the current project only (cache.json, state.json, cache.stat.json); preserves diagnostics + token-sample history.
config
Read or modify creditgauge runtime config — switch statuslineTemplate to a preset, or disable/enable the upstream chain.
install
Install the creditgauge (CreditGauge) statusline wrapper into Claude Code's settings.json (for uninstall use the dedicated :uninstall slash command).
clean-journal
Remove old .jsonl journal files under state/ / by age or --all.
uninstall
Uninstall creditgauge (CreditGauge), restore settings.json, and wipe the plugin's cache, marketplace, and loader rows.