wicked-garden-engineering

wicked-garden-engineering is a skill for Claude Code from mikeparcewski/wicked-garden. It costs 285 tokens per session (2,430 once invoked), scanned A, original, MIT.

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

In plain words
What is it for?
Use it for code or diff reviews, architecture checks, debugging, implementation plans, documentation, and mechanical changes across multiple files.
Why use it?
It gives a structured way to assess code and plan work, reducing missed problems and unclear implementation decisions.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the wicked-garden plugin — 147 skills, 5 commands, 1 agent, 13 hooks shipped together

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

Compare 6 skills from other repositories ↓
Install

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.

Claude Code
/plugin marketplace add mikeparcewski/wicked-garden
Claude Code
/plugin install wicked-garden

Made for: Claude Code.

Or install wicked-garden, the plugin that ships this one along with the rest of its 147 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.

agentmods badge for wicked-garden-engineering

README.md
[![agentmods](https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/engineering.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.svg" alt="Measured on agentmods" height="20"></a>
Per session 285 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,430 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00285 $0.02430
Opus 5 $0.00143 $0.01215
Sonnet 5 $0.00057 $0.00486
Haiku 4.5 $0.00028 $0.00243

Measured 8d ago against content hash a4c2a493b174, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-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 8d 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 · 197 lines

How it starts

The opening of the file, as written. The whole thing — 197 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 dispatches to the fork workers listed at the end.

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

  1. Parse scope (path or git-diff target), --focus, --persona, and --scenarios.
  2. Read("${CLAUDE_PLUGIN_ROOT}/skills/engineering/refs/review.md") — 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.
  3. Persona branch (only if --persona <name> present): resolve the persona via scripts/persona/registry.py --get {name} --json. If found, apply the review through that persona's frame. If not found, warn and fall through.
  4. 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.
  5. 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 · 197 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.

  1. 8d 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 285 tokens to every session and 2,430 once invoked, about $0.0014 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.

Related

Other skills, from other repositories

adversarial-reviewer

Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.

emdash-cms/emdash · 71 tokens

gsd-ns-review

Route to the appropriate quality / review skill based on the user's intent. gsd-code-review-fix was absorbed by gsd-code-review --fix in #2790.

open-gsd/gsd-core · 16 tokens

issue

Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…

jeremylongshore/tons-of-skills-marketplace · 115 tokens

gitnexus

A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.

hashgraph-online/awesome-codex-plugins · 58 tokens

cleanup-code-inspections

Reduce technical debt and improve code quality by systematically resolving static analysis warnings.

flutter/flutter-intellij · 19 tokens

superlint

This skill describes the mandatory standard operating procedure for using our internal SuperLint tool. Use this when tasks require fixing code quality issues according to corporate standards.

mgechev/skillgrade · 0 tokens