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.
git clone --depth 1 https://github.com/DropFan/claude-code-pluginsWrote 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/dropfan/claude-code-plugins/update-plugins)<a href="https://agentmods.dev/commands/dropfan/claude-code-plugins/update-plugins"><img src="https://agentmods.dev/badge/commands/dropfan/claude-code-plugins/update-plugins/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.
<a href="https://agentmods.dev/commands/dropfan/claude-code-plugins/update-plugins"><img src="https://agentmods.dev/badge/commands/dropfan/claude-code-plugins/update-plugins.svg" alt="Reviewed on agentmods" width="80" 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.00010 | $0.00149 |
| Opus 5.5 | $0.00004 | $0.00060 |
| Sonnet 5.5 | $0.00002 | $0.00030 |
| Haiku 4.5 | $0.00001 | $0.00015 |
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 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.
What it actually says
Update All Plugins
Run the following steps to update all installed plugins:
- Run
claude plugin listto get the list of installed plugins - Parse the output to extract all plugin identifiers (format:
name@marketplace) - For each plugin, run
claude plugin update <plugin-identifier>and collect the results - After all updates complete, display a summary table showing each plugin and its update result (updated / already up-to-date / failed)
- Remind the user to restart the session to apply updates
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.
- 1mo ago First seen · 15 lines · 10 tokens per session scan A 80ba5d8ca895
update-plugins is a command published in the GitHub repository DropFan/claude-code-plugins (8 stars, last pushed 27d ago), licensed MIT. It adds 10 tokens to every session and 149 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.
Other commands, from other repositories
prompt
System instructions for writing effective prompts. Apply when generating commands, skills, agents, or any LLM instructions.
full
Run the full hope pipeline — intent, shape, target, freeze as needed — then execute.
status
Show tlive daemon, channel, and Codex companion status.
csv-to-numbers
Convert a CSV into a formatted Numbers workbook.
close
Close out a Linear issue — move to Done, add a closing comment, and clean up the local branch/worktree.
prompt
Convert a rough ask into a structured XML-tagged prompt using the factory-prompting vocabulary.