Claude Code Plugins Directory is a marketplace containing plugins for Claude Code, including tools, commands, skills, agents, hooks, and model context servers. Claude Code users browse it to install Anthropic-maintained or approved third-party extensions.
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.
/plugin marketplace add anthropics/claude-plugins-official/plugin install code-modernizationWrote 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/anthropics/claude-plugins-official/modernize)<a href="https://agentmods.dev/commands/anthropics/claude-plugins-official/modernize"><img src="https://agentmods.dev/badge/commands/anthropics/claude-plugins-official/modernize/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/anthropics/claude-plugins-official/modernize"><img src="https://agentmods.dev/badge/commands/anthropics/claude-plugins-official/modernize.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.00000 | $0.01100 |
| Opus 5.5 | $0.00000 | $0.00440 |
| Sonnet 5.5 | $0.00000 | $0.00220 |
| Haiku 4.5 | $0.00000 | $0.00110 |
Grade A, and why
modernize 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 20d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- modernize — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the front door of a guided modernization. The person may know nothing about modernization: ask little, explain in plain words, and always end on one exact command to run next.
1 — Find where things stand
- If
$systemwas given, use it. Otherwise look atanalysis/andlegacy/: one system means use it, several means ask which (pop-up), none means ask where the code is (step 2). - If
analysis/$system/already has files, this is a return visit: do what/code-modernization:modernize-status $systemdoes (where they are, what is stale) in five lines, and end on the exact next command. Stop there.
2 — Find the code
The code is legacy/$system (a copy, or a symlink to where it really lives). If it is not there yet, ask where it is
(this folder, another folder, or a git URL: clone into legacy/<name> after they agree). If $ARGUMENTS has
--source <path>, use that path. Pick a short name for it (letters, digits, - and _) if none was given. Say in one
line what you found there (languages and rough size: scc or a quick file count is enough).
3 — Ask what they want (two short pop-ups at most)
Use the AskUserQuestion tool, never chat text; without it (a headless run) pick the defaults and record them as open items. A pop-up allows at most four options per question, and the person can always type their own answer.
Pop-up 1, two questions:
- What do you want to do with it? Move to a newer version of the same technology (for example .NET Framework to .NET 8, Java 8 to 17, Python 2 to 3), Rewrite it in a different technology, one piece at a time, while the old system keeps running, Rebuild it from scratch on a new architecture, Understand it first: map it and list what it does (also the right choice when they are not sure: the assessment then recommends one of the other three).
- What must stay true? Pick any: The old system keeps running during the move, Behavior must match exactly, including known quirks, Fix known bugs as we go, A security review comes first. Choosing none means nothing special.
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.
- 20d ago First seen · 65 lines · 0 tokens per session scan A fc3ba0a9a3e3
modernize is a command published in the GitHub repository anthropics/claude-plugins-official (39,070 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,100 tokens. 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-09-26.
Other commands, from other repositories
spec-forge
Use when generating software specifications — full chain ([Idea]→[Decompose]→[PRD]→SRS→Tech Design→Review) or individual documents.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
release
Git geçmişinden hedef kitleye uygun sürüm notları oluştur.
rclone_config_dump
Dump the config file as JSON.
dd-spec-test
Generate test spec (requires confirmed status).
dd-init
Initialize product documentation structure in current directory.