A command that removes old numbered versions from an add-on's cache and keeps only the newest version. It can preview the removals first with a dry run.

Use it to clean unused plugin versions while leaving non-version folders, files, and the active status-line wrapper untouched.

Old cached versions can take up substantial disk space even though the add-on uses only the newest one.

clean-cache — Command for coding agents by cwf818: A command that removes old numbered versions from an…

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.

agentmods

npx agentmods add commands/cwf818/topgauge/clean-cache

Clone the repo

git clone --depth 1 https://github.com/cwf818/topgauge

Or install creditgauge, the plugin that ships this one along with the rest of its 4 commands.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/cwf818/topgauge/clean-cache.svg)](https://agentmods.dev/commands/cwf818/topgauge/clean-cache)

Your own site

<a href="https://agentmods.dev/commands/cwf818/topgauge/clean-cache"><img src="https://agentmods.dev/badge/commands/cwf818/topgauge/clean-cache.svg" alt="Measured on agentmods" height="20"></a>

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 468 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00013	$0.00468
Opus 5	$0.00006	$0.00234
Sonnet 5	$0.00003	$0.00094
Haiku 4.5	$0.00001	$0.00047

Measured 3d ago against content hash 025cdbe961fd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 3d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

clean-cache — 100% identical, 0 lines differ

commands/clean-cache.md · 45 lines

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.10 sorts AFTER 0.2.9).
Keeps the newest. Removes the rest.
Supports --dry-run for 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

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.

3d ago First seen · 45 lines · 13 tokens per session scan A 025cdbe961fd

Subscribe to this mod's changes

clean-cache is a command published in the GitHub repository cwf818/topgauge (2 stars, last pushed 1mo ago), 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

balance claude-code-plugin deepseek minimax quota statusline

clean-cache

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

Copies of this mod

What it actually says

creditgauge :clean-cache

What this file has done since we first saw it

Other commands, from other repositories

clean

reset

config

install

clean-journal

uninstall