agentmods.dev

clear-plugin-cache

clear-plugin-cache is a command for Claude Code from signalcompose/claude-tools. It costs 12 tokens per session (607 once invoked), scanned A, original, MIT.

A command that clears cached Claude Code plugin files. A cache is stored data that can cause an old plugin version to be used after an update.

In plain words
What is it for?
Use it to clear the cache for one plugin, a marketplace, or all supported cached plugins.
Why use it?
It fixes cases where /plugin update changes the repository but Claude Code still loads stale plugin files.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths; mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the utils plugin — 2 commands shipped together

not rated 4repo 1mo ago A scan 12 tokens original MIT

Good fit Use it to clear the cache for one plugin, a marketplace, or all supported cached plugins.

Compare 6 commands from other repositories ↓
View source ↗ signalcompose/claude-tools
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add signalcompose/claude-tools
Claude Code
/plugin install utils

Made for: Claude Code.

Or install utils, the plugin that ships this one along with the rest of its 2 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.

agentmods badge for clear-plugin-cache

README.md
[![agentmods](https://agentmods.dev/badge/commands/signalcompose/claude-tools/clear-plugin-cache/github.svg)](https://agentmods.dev/commands/signalcompose/claude-tools/clear-plugin-cache)
Your own site
<a href="https://agentmods.dev/commands/signalcompose/claude-tools/clear-plugin-cache"><img src="https://agentmods.dev/badge/commands/signalcompose/claude-tools/clear-plugin-cache/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for clear-plugin-cache

Your own site · 80×15
<a href="https://agentmods.dev/commands/signalcompose/claude-tools/clear-plugin-cache"><img src="https://agentmods.dev/badge/commands/signalcompose/claude-tools/clear-plugin-cache.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 607 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00012 $0.00607
Opus 5.5 $0.00005 $0.00243
Sonnet 5.5 $0.00002 $0.00121
Haiku 4.5 $0.00001 $0.00061

Measured 1mo ago against content hash a8b96b7b1317, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

clear-plugin-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 1mo 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.

plugins/utils/commands/clear-plugin-cache.md · 58 lines

What it actually says

Clear Plugin Cache

This command clears the plugin cache to resolve stale version issues caused by Claude Code's cache invalidation bug.

Background

When running /plugin update, Claude Code updates the marketplace git repository but does not invalidate the cached plugin files. This causes updated plugins to not work correctly until the cache is manually cleared.

Related issues:

  • #14061 - /plugin update does not invalidate plugin cache
  • #15642 - CLAUDE_PLUGIN_ROOT points to stale version

Sandbox要件

重要: このコマンドはプラグインキャッシュファイルの削除のためsandboxバイパスが必要です。

dangerouslyDisableSandbox: trueで実行する理由:

  • 操作: ~/.claude/plugins/cache/内のディレクトリを削除
  • Sandbox制限: デフォルトでは書き込み操作がブロックされる
  • 安全な操作: ユーザーが開始したキャッシュクリーンアップ、システム変更のリスクなし

Usage

以下のBashコマンドを即座に実行してください:

重要: ファイル削除のためdangerouslyDisableSandbox: trueを使用してください。

Bash toolで実行:

  • コマンド: bash ${CLAUDE_PLUGIN_ROOT}/scripts/clear-plugin-cache.sh "$ARGUMENTS"
  • dangerouslyDisableSandbox: true（必須）

Arguments

Argument Description
plugin-name Name of the plugin to clear cache for
--marketplace <name> Specify marketplace (default: claude-tools)
--all Clear all plugin caches for the specified marketplace
--dry-run Show what would be deleted without actually deleting
-y, --yes Skip confirmation prompt (useful for automated workflows)

Examples

  • Clear single plugin: /utils:clear-plugin-cache cvi
  • Clear with marketplace: /utils:clear-plugin-cache plugin --marketplace other-market
  • Clear all: /utils:clear-plugin-cache --all --marketplace claude-tools
  • Clear all (skip confirmation): /utils:clear-plugin-cache --all --marketplace claude-tools -y
  • Dry run: /utils:clear-plugin-cache cvi --dry-run

After Clearing

After clearing the cache, restart Claude Code for changes to take effect.

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.

  1. 1mo ago First seen · 58 lines · 12 tokens per session scan A a8b96b7b1317

Subscribe to this mod's changes

clear-plugin-cache is a command published in the GitHub repository signalcompose/claude-tools (4 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 607 once invoked, about $0.0000 per session on Opus 5.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.

Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens

speckit.bug.fix

Apply the remediation from a bug assessment and record what was changed.

github/spec-kit · 12 tokens