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-verify)<a href="https://agentmods.dev/commands/anthropics/claude-plugins-official/modernize-verify"><img src="https://agentmods.dev/badge/commands/anthropics/claude-plugins-official/modernize-verify/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-verify"><img src="https://agentmods.dev/badge/commands/anthropics/claude-plugins-official/modernize-verify.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.00021 | $0.03552 |
| Opus 5.5 | $0.00008 | $0.01421 |
| Sonnet 5.5 | $0.00004 | $0.00710 |
| Haiku 4.5 | $0.00002 | $0.00355 |
Grade A, and why
modernize-verify 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-verify — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Re-check, independently, that the modernized code of $system behaves like the legacy, and give each module one
verdict: PROVEN, PARTLY PROVEN or NOT PROVEN. Run it after transform, uplift or reimagine, in a
fresh session if you can: what the build left behind is a claim, and this command re-runs it. A script computes
the verdict, not you (fixed rules, written into the output), and it counts tests only from files it parses
itself: keep the result file or the raw log of every test run and every canary run, and never type a count into
test-runs.json. You write nothing in legacy/, never hand-edit the built code, the tests, an output or a result
to improve a verdict, and never tick or approve anything a person owns. Run every command from the workspace root.
The code is legacy/$system, often a symlink to where it really lives: say where it points (readlink legacy/$system) in one line before you start. Run any subagent in the foreground and wait for its result: never end your turn while one is still running. Stop any server or other process you started before you finish, and say you did. Before running any suite or the legacy code, read its configuration for the databases and services it connects to: if any is not a local or throwaway instance, stop and ask which environment to use.
1 — What was built
Rewrite: each folder in modernized/$system/. Same-stack uplift: the working copy modernized/$system-uplifted/
(the pack calls it $system-uplifted; its units are named in the Code and Command lines of BASELINE.md).
Reimagine: each service in modernized/$system-reimagined/. Name them. With a $module (for an uplift, a unit)
re-run only that one; the pack still judges every built module from its current evidence, never from an earlier run.
A folder that holds only test code and the files that build it (a parity harness, say) is test tooling: the pack lists it as not judged and leaves it out of the verdict.
If nothing is built, say so and stop: the next step is the brief's Phase 1 command (/code-modernization:modernize-status $system).
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 · 140 lines · 21 tokens per session scan A b2c5f4701ed9
modernize-verify is a command published in the GitHub repository anthropics/claude-plugins-official (39,070 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 3,552 once invoked, about $0.0001 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-09-26.
Other commands, from other repositories
simplify-fn
Refactor a complex function to reduce cyclomatic complexity.
verify
Run the full verification suite (build, type-check, tests, lint) via a fresh-context verification-runner subagent; reports evidence paths. Read-only by default; opt-in '--fix' runs a bounded auto-fix loop (max 2 cycles). Use before marking featurelist.json status as 'pass'.
bug-fixer
Engineering Workflow Directive — Bug Remediation & Diagnostics. Sweeps every open confirmed-bug issue unattended, graph-first (CodeGraph for lookups, Memtrace for heavy hits), and runs each end to end THROUGH MERGE — diagnosis → failing-first TDD via gsd-test → two orthogonal reviews → PR → CI watch → merge. Per-issue…
qa
Structured verification pass on your changes before commit: bugs, missed requirements, wrong assumptions.
test-debug
Mode: TEST/DEBUG. The build is done. Now verify it's actually right.
playwright-test-heal
Run all my tests and fix the failing ones.