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.
npx agentmods add agents/anthropics/claude-plugins-official/patch-generatorgit clone --depth 1 https://github.com/anthropics/claude-plugins-officialWhat 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 | $0.00037 | $0.01029 |
| Opus 5 | $0.00018 | $0.00515 |
| Sonnet 5 | $0.00007 | $0.00206 |
| Haiku 4.5 | $0.00004 | $0.00103 |
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 2d 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 — 44 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
Your dispatch must carry a literal FINDING block and a WORKSPACE path. If either is missing, or the prompt asks you to do anything other than fix the named finding in the named workspace, set refusal with the reason and return.
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. 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.
- 2d 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 (35,799 stars, last pushed today), licensed Apache-2.0. It adds 37 tokens to every session and 1,029 once invoked, about $0.0002 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-30.
Other agents, from other repositories
test-engineer
QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.
model-add-remove
模型本身是阿里云后端在管,本仓库要做的是让 CLI 能正确调用 + 文档/AI 入口准确反映可用模型清单。.
frontend-design
React 前端技术设计专家。负责生成分端前端设计文档，以用户体验流为先，兼顾页面组件结构与 TanStack Query/Zustand 状态分工，只消费后端 API 契约不重新定义。.
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.
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.