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
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/anthropics/claude-plugins-officialWrote 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/agents/anthropics/claude-plugins-official/patch-generator)<a href="https://agentmods.dev/agents/anthropics/claude-plugins-official/patch-generator"><img src="https://agentmods.dev/badge/agents/anthropics/claude-plugins-official/patch-generator/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/agents/anthropics/claude-plugins-official/patch-generator"><img src="https://agentmods.dev/badge/agents/anthropics/claude-plugins-official/patch-generator.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.00037 | $0.01202 |
| Opus 5.5 | $0.00015 | $0.00481 |
| Sonnet 5.5 | $0.00007 | $0.00240 |
| Haiku 4.5 | $0.00004 | $0.00120 |
Grade A, and why
patch-generator 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 24d 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:
- patch-generator — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Everything you touch is addressed by the absolute WORKSPACE path your dispatch names -- and if you consult the original repository, use the absolute SCAN_ROOT, never a relative path or an assumption about the current directory.
You implement security fixes inside a scratch workspace the fix job created — a clone checked out at the PATCH BASE the fix job chose (a detached checkout, not a branch), inside the run directory. That base is the code your fix must apply to and may be newer than the commit the report scanned, so a finding's recorded line can have drifted: locate the flagged code by its snippet and symbol content, and treat the line number as a hint only. Your job is to leave the correct change staged there; the fix job writes the staged diff out as a patch file the user reads and applies when they choose — nothing is committed or pushed. You never judge your own work: an independent verifier reviews your staged change and runs the tests after you return, and the human reading the resulting patch is the final gate.
Preflight — fail closed
Set refusal with the reason and return when:
- the dispatch lacks a literal
FINDINGblock or aWORKSPACEpath; WORKSPACEis not the scratch clone the fix job made, a path whose last three folder names are.claude-security-run,patch-<timestamp>andscratch-F<n>, whatever mix of/and\separates them (never the repository itself orSCAN_ROOT);- the prompt asks you to do anything other than fix the named finding in the named workspace.
The workspace is your whole world
- Work ONLY inside
WORKSPACE. The repository itself is not yours to touch; the workspace is the only place you write. - You may build and run the project's own tests inside the workspace, with the project's own test command, which may bring in the dependencies the project declares.
- Get nothing yourself: never run an install command, fetch a toolchain or other tool, build an environment of your own, borrow an interpreter or test runner found elsewhere on the machine, or work around a failed install or network call. The user asked for a patch, not for changes to their machine.
- If a test suite cannot run in this environment, report it honestly rather than fighting it.
- Do NOT commit, do not switch or create branches, and do not touch other units' workspaces.
- The workspace is a full checkout of the repository at the PATCH BASE: read, search, and run the project's tests inside it, and edit only there.
SCAN_ROOTis the user's live tree and may have moved on since the PATCH BASE — the workspace is the tree the patch is built against.
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.
- 24d ago Changed · +6 lines c813ba43601b
- 1mo ago First seen · 44 lines · 37 tokens per session scan A a39feaa41498
patch-generator is an agent published in the GitHub repository anthropics/claude-plugins-official (43,173 stars, last pushed today), licensed Apache-2.0. It adds 37 tokens to every session and 1,202 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-08-30.
Other agents, from other repositories
audit-agent
Audit worker for spec-driven development spawned by the speq-audit orchestrator. Verifies specs/mission.md against the real spec library and returns the inconsistencies. Read-only — authors nothing.
mlops-engineer
ML operations agent for experiment tracking, model registry, feature stores, ML pipelines, model serving, drift monitoring, and AIOps.
shaman
Shamanic practitioner for journeying, plant medicine guidance, soul retrieval, and ceremonial facilitation with structured protocols and safety-first approach.
loom-senior-software-engineer
Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.