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 skills/mikeparcewski/wicked-garden/patchnpx skills add mikeparcewski/wicked-garden --skill patchgit clone --depth 1 https://github.com/mikeparcewski/wicked-gardenWrote 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/skills/mikeparcewski/wicked-garden/patch)<a href="https://agentmods.dev/skills/mikeparcewski/wicked-garden/patch"><img src="https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/patch.svg" alt="Measured on agentmods" 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 | $0.00177 | $0.02073 |
| Opus 5 | $0.00088 | $0.01037 |
| Sonnet 5 | $0.00035 | $0.00415 |
| Haiku 4.5 | $0.00018 | $0.00207 |
Grade A, and why
wicked-garden-engineering-patch 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wicked-patch
Generate and propagate code changes across your entire codebase using the symbol graph.
All sub-actions run the patch CLI. The full invocation is:
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/engineering/patch/patch.py" <sub-action> [args]
Examples below abbreviate this to patch.py <sub-action> … — always run the full form.
The propagation diagram, quick-start recipes, per-action examples, the sample
PROPAGATION PLAN / GENERATED PATCHES output, the patches-file JSON schema,
and the language/type/SQL-dialect reference tables live in
refs/output-samples.md.
Sub-actions
| Sub-action | Purpose |
|---|---|
patch-plan |
Show what would be affected — propagation preview, no patches |
add-field |
Add field with propagation |
rename |
Rename across all usages |
remove |
Remove field everywhere (DELETES code — see warning) |
apply |
Apply saved patches from a JSON file |
new-generator |
Author a new language generator (refs/new-generator.md) |
patch-plan — propagation preview
Show what would be affected by a change without generating patches. Distinct
from the engineering domain skill's plan action (a human implementation plan
with risks and tests) — patch-plan is the impact preview for mechanical patches.
The CLI subcommand is plan.
Arguments: symbol_id (required — symbol to analyze); --change
(add_field | rename_field | remove_field | modify_field); --depth
(max traversal depth, default 5); --json (output as JSON).
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/engineering/patch/patch.py" plan "<symbol_id>" --change "<change_type>" [--json]
See refs/output-samples.md for examples and the sample PROPAGATION PLAN output.
add-field — add a field and propagate
Add a field to an entity/class and propagate to all affected files.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 191 lines · 177 tokens per session scan A d79e9f6e48ab
wicked-garden-engineering-patch is a skill published in the GitHub repository mikeparcewski/wicked-garden (9 stars, last pushed today), licensed MIT. It adds 177 tokens to every session and 2,073 once invoked, about $0.0009 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…