update-plugins

A command that checks all installed Claude Code plugins and updates each one to its newest available version.

In plain words
What is it for?
Use it to update the complete installed plugin set and receive a summary of each plugin's update result. A session restart may be needed afterward.
Why use it?
It removes the repetitive work of finding plugins one by one and running separate update commands, while reporting failures or plugins that were already current.

Command

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/dropfan/claude-code-plugins/update-plugins
Clone the repo
git clone --depth 1 https://github.com/DropFan/claude-code-plugins
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 149 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.

ModelPer sessionOnce invoked
Fable 5 $0.00010 $0.00149
Opus 5 $0.00005 $0.00075
Sonnet 5 $0.00002 $0.00030
Haiku 4.5 $0.00001 $0.00015

Measured yesterday against content hash 80ba5d8ca895, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

update-plugins 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 yesterday.

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/update-plugins/commands/update-plugins.md · 15 lines

What it actually says

Update All Plugins

Run the following steps to update all installed plugins:

  1. Run claude plugin list to get the list of installed plugins
  2. Parse the output to extract all plugin identifiers (format: name@marketplace)
  3. For each plugin, run claude plugin update <plugin-identifier> and collect the results
  4. After all updates complete, display a summary table showing each plugin and its update result (updated / already up-to-date / failed)
  5. Remind the user to restart the session to apply updates
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. yesterday First seen · 15 lines · 10 tokens per session scan A 80ba5d8ca895

Subscribe to this mod's changes

update-plugins is a command published in the GitHub repository DropFan/claude-code-plugins (7 stars, last pushed 26d ago), licensed MIT. It adds 10 tokens to every session and 149 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.