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/signalcompose/claude-tools/clear-plugin-cachegit clone --depth 1 https://github.com/signalcompose/claude-toolsWhat 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.00012 | $0.00607 |
| Opus 5 | $0.00006 | $0.00303 |
| Sonnet 5 | $0.00002 | $0.00121 |
| Haiku 4.5 | $0.00001 | $0.00061 |
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 2d 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
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 updatedoes 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.
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.
- 2d ago First seen · 58 lines · 12 tokens per session scan A a8b96b7b1317
clear-plugin-cache is a command published in the GitHub repository signalcompose/claude-tools (4 stars, last pushed 5d ago), licensed MIT. It adds 12 tokens to every session and 607 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
checklist
Generate a custom checklist for the current feature based on user requirements.
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.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.