What is wicked-garden-engineering?

An engineering guide for reviewing code, checking system design, finding bugs, planning changes, and writing documentation.

Use it for code or diff reviews, architecture checks, debugging, implementation plans, documentation, and mechanical changes across multiple files.

It gives a structured way to assess code and plan work, reducing missed problems and unclear implementation decisions.

wicked-garden-engineering — Skill for Claude Code by mikeparcewski

Install

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.

Any agent

npx skills add mikeparcewski/wicked-garden --skill engineering

Clone the repo

git clone --depth 1 https://github.com/mikeparcewski/wicked-garden

Made for: Claude Code.

Or install wicked-garden, the plugin that ships this one along with the rest of its 145 skills, 5 commands, 1 agent, 13 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/engineering/github.svg)](https://agentmods.dev/skills/mikeparcewski/wicked-garden/engineering)

Your own site

<a href="https://agentmods.dev/skills/mikeparcewski/wicked-garden/engineering"><img src="https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/engineering/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/mikeparcewski/wicked-garden/engineering"><img src="https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/engineering.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 230 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,693 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00230	$0.02693
Opus 5.5	$0.00092	$0.01077
Sonnet 5.5	$0.00046	$0.00539
Haiku 4.5	$0.00023	$0.00269

Measured 15d ago against content hash 37a8e3f3dded, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

wicked-garden-engineering 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 15d 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.

skills/engineering/SKILL.md · 211 lines

How it starts

The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Engineering

Senior engineering guidance on code quality, architecture, and implementation. The five actions below run inline (no dispatch); genuinely structural, migration, or API-reference work hands off to the workers listed at the end.

Runtime

Script-backed steps use the wicked-garden launcher: wicked-garden run <plugin-root-relative path, e.g. scripts/…> [args]. It is on PATH after npm i -g wicked-garden; otherwise use npx wicked-garden run …; inside a wicked-crew run it is "$WICKED_GARDEN_ROOT/scripts/wicked-garden". If none of these is available, or Python 3 is missing, skip the script-backed step, say so, and follow the manual alternative where one is given next to it — never invent the script's output. Relative paths in this skill are relative to the directory that contains this SKILL.md.

Routing

Ask	Action
Code-level quality review of files or a diff	§ review
Component/system-level architecture review	§ arch
Bug / error / unexpected-behavior diagnosis	§ debug
Implementation plan before writing code	§ plan
Generate or refresh documentation	§ docs
Multi-file mechanical change (add-field/rename/remove)	patch

Review disambiguation: this skill reviews source code. For an AI agent system use agentic review, for a UI use product ux-review, and for a binding go/no-go verdict use archetype review (see docs/domains.md → "review appears in three domains"). arch is component/system-level review; review is code-level; greenfield design is the architecture module.

review — senior-engineer code review

Parse scope (path or git-diff target), --focus, --persona, and --scenarios.
Read refs/review.md (relative to this skill's base directory) — R1–R6 Bulletproof Coding Standards, T1–T6 Bulletproof Testing Standards, agent overstepping checklist, focus lane definitions, persona routing instructions, wicked-scenarios format, and output template.
Persona branch (only if --persona <name> present): resolve the persona via wicked-garden run scripts/persona/registry.py --get {name} --json. If found, apply the review through that persona's frame. If not found, warn and fall through.
Read the target file(s) / diff. Apply R1–R6 to all code; add T1–T6 when --focus tests or reviewing test files. If --focus given, deepen that lane. Flag agent overstepping (scope creep, commented-out code, over-engineering) with file:line citations. Flag every piece of custom code that duplicates a built-in of the chosen framework or library: cite the code and the built-in, and judge the author's stated reason (refs/review.md, "Duplicates of a built-in").
Emit the standard Engineering Review output (Strengths, Issues table with rule + location, Architecture Notes, Maintainability Concerns, Agent Overstepping, Recommendations). If --scenarios, append wicked-scenarios blocks for each Critical/High finding.

Read the full file on GitHub · 211 lines

Files

What ships with it

60 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.

Changes

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.

15d ago Changed · +6 lines 37a8e3f3dded
1mo ago Changed · +4 lines · -55 tokens per session 6f6715344ea0
1mo ago Changed · +4 lines 272a07a95757
1mo ago First seen · 197 lines · 285 tokens per session scan A a4c2a493b174

Subscribe to this mod's changes

wicked-garden-engineering is a skill published in the GitHub repository mikeparcewski/wicked-garden (9 stars, last pushed today), licensed MIT. It adds 230 tokens to every session and 2,693 once invoked, about $0.0009 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-31.

Code review Debugging Testing agent-skills claude-code-plugin coding-agents mcp

cypress-debugger

Use when a Cypress end-to-end test has already run and failed and the user wants the root cause and a concrete fix. Trigger on a failing Cypress spec, Timed-out-retrying command, unresolved selector, cy.intercept alias or request race, suite-breaking hook, retry-only flake, hydration or timing race, or a…

voidmatcha/e2e-skills · 158 tokens

playwright-debugger

Use when a Playwright end-to-end test has already run and failed and the user wants the root cause and a concrete fix. Trigger on a failing Playwright spec, TimeoutError, broken or ambiguous selector, post-deploy suite failure, retry-only flake, hydration or timing race, or a passes-locally-but-fails-in-CI split.…

voidmatcha/e2e-skills · 163 tokens

ia-verification-before-completion

Enforces fresh verification evidence before any completion claim. Use when about to claim "tests pass", "bug fixed", "done", "ready to merge", handing off work, or before editing when a request has ambiguous scope.

iliaal/whetstone · 52 tokens

debug

Systematic bug investigation with a five-phase framework: reproduce, narrow, diagnose, fix, verify. Supports automated regression bisect via --regression flag. Produces a structured debug report with root cause analysis, regression test, and CQ/Q self-evaluations.

greglas75/zuvo · 55 tokens

Vitest Mock Isolation Review

Detects Vitest test-isolation hazards: unrestored vi.spyOn/vi.mock without afterEach cleanup or restoreMocks config, un-awaited resolves/rejects assertions, and shared mutable module state across tests.

s977043/river-review · 48 tokens

bug-report-reproduce

Reproduce a user, customer, or support-reported problem with synthetic data, prove the cause with a temporary test, record a narrated click-through walkthrough of the symptom, and report what was and was not proven. Use when the user links a bug report, support thread, or ticket and asks to reproduce it, find the…

yarlson/yarstack · 102 tokens