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/clean-cachegit 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/clean-cache)<a href="https://agentmods.dev/commands/cwf818/creditgauge/clean-cache"><img src="https://agentmods.dev/badge/commands/cwf818/creditgauge/clean-cache.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.00013 | $0.00468 |
| Opus 5 | $0.00006 | $0.00234 |
| Sonnet 5 | $0.00003 | $0.00094 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
clean-cache 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.
This is a copy
100% identical to clean-cache — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
creditgauge :clean-cache
Targets the version directories that accumulate under the plugin
cache after every /plugin install roll-forward:
${CLAUDE_CONFIG_DIR:-$HOME/.claude}/plugins/cache/creditgauge/creditgauge/
0.2.7/ ← old, no longer used
0.2.7.1/ ← old, no longer used
0.2.8/ ← currently live
The statusLine.command written by :install is version-independent —
it ls -ds every version dir, sorts by version, and execs the
highest. So old version dirs are pure dead weight (~40-50MB each: full
source tree + node_modules). This command:
- Walks the cache, finds all
^[0-9]+\.[0-9]+\.[0-9]+(\.[0-9]+)?$dirs (3- or 4-component versions; everything else is treated as decoy and left alone —1.2,.orphaned_at_*,not-a-version, etc.). - Sorts numerically (not lexically —
0.2.10sorts AFTER0.2.9). - Keeps the newest. Removes the rest.
- Supports
--dry-runfor preview. - Does NOT touch any non-version dir, any file, or the wrapper statusline itself. Idempotent: re-running is a no-op once only the newest remains.
After :clean-cache you can run :install (or /plugin install creditgauge@creditgauge) again to refresh the remaining dir, or
just leave it — install.sh will detect the carried state from
the previous version automatically.
Execute the clean-cache script with whatever arguments were passed to this command:
"${CLAUDE_PLUGIN_ROOT}/scripts/clean-cache.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 · 45 lines · 13 tokens per session scan A 025cdbe961fd
clean-cache is a command published in the GitHub repository cwf818/creditgauge (2 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 468 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to clean-cache, differing in 0 lines, and is treated as a copy.
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.