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.
/plugin marketplace add mikeparcewski/wicked-garden/plugin install 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/engineering)<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>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.00285 | $0.02430 |
| Opus 5 | $0.00143 | $0.01215 |
| Sonnet 5 | $0.00057 | $0.00486 |
| Haiku 4.5 | $0.00028 | $0.00243 |
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.
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
- Parse scope (path or git-diff target),
--focus,--persona, and--scenarios. 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.- Persona branch (only if
--persona <name>present): resolve the persona viascripts/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 testsor reviewing test files. If--focusgiven, deepen that lane. Flag agent overstepping (scope creep, commented-out code, over-engineering) withfile:linecitations. - 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.
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.
- architecture/refs/adr-template.md 4.4 KB
- architecture/refs/architecture-template-deployment.md 4.3 KB
- architecture/refs/architecture-template-design.md 5.9 KB
- architecture/refs/examples-ecommerce-analytics.md 6.9 KB
- architecture/refs/examples-saas-trading.md 6.5 KB
- architecture/refs/patterns-advanced.md 8.1 KB
- architecture/refs/patterns-structural.md 9.0 KB
- architecture/SKILL.md 4.7 KB
- backend/refs/checklists.md 3.3 KB
- backend/refs/patterns.md 4.1 KB
- backend/SKILL.md 2.7 KB
- debugging/refs/patterns.md 5.1 KB
- debugging/refs/process.md 3.9 KB
- debugging/SKILL.md 3.1 KB
- docs/SKILL.md 3.0 KB
- frontend/refs/checklists.md 2.1 KB
- frontend/refs/patterns.md 2.9 KB
- frontend/SKILL.md 2.7 KB
- integration/refs/error-handling-best-practices.md 2.8 KB
- integration/refs/error-handling-error-classes-typescript.md 4.2 KB
- integration/refs/error-handling-error-response-format.md 5.7 KB
- integration/refs/error-handling-retry-strategies.md 3.7 KB
- integration/refs/event-schemas-best-practices.md 3.8 KB
- integration/refs/event-schemas-event-naming-conventions.md 4.7 KB
- integration/refs/event-schemas-event-structure.md 5.5 KB
- integration/refs/graphql-best-practices.md 2.2 KB
- integration/refs/graphql-error-handling.md 3.5 KB
- integration/refs/graphql-graphql-basics.md 3.0 KB
- integration/refs/graphql-query-examples.md 2.7 KB
- integration/refs/graphql-schema-design-patterns.md 4.5 KB
- integration/refs/grpc-grpc-overview.md 4.4 KB
- integration/refs/grpc-implementation-examples.md 6.2 KB
- integration/refs/grpc-metadata-headers.md 5.9 KB
- integration/refs/grpc-testing.md 1.1 KB
- integration/refs/openapi-template.yaml 17 KB
- integration/refs/resilience-best-practices.md 2.4 KB
- integration/refs/resilience-circuit-breaker-pattern.md 7.0 KB
- integration/refs/resilience-rate-limiting.md 5.2 KB
- integration/refs/resilience-timeout-pattern.md 4.3 KB
- integration/refs/rest-api-fundamentals.md 5.2 KB
- integration/refs/rest-api-responses-security.md 6.5 KB
- integration/refs/versioning-breaking-changes.md 4.4 KB
- integration/refs/versioning-migration-strategies.md 4.7 KB
- integration/refs/versioning-versioning-strategies.md 4.4 KB
- integration/SKILL.md 5.3 KB
- large-scale-migration/SKILL.md 9.8 KB
- patch/refs/new-generator.md 6.3 KB
- patch/refs/output-samples.md 6.6 KB
- patch/SKILL.md 7.9 KB
- refs/arch.md 4.5 KB
- refs/debug.md 4.0 KB
- refs/docs.md 5.7 KB
- refs/engineering-checklists.md 2.7 KB
- refs/engineering-templates.md 1.2 KB
- refs/plan.md 3.6 KB
- refs/review.md 6.2 KB
- system-design/refs/anti-patterns-big-ball-of-mud.md 5.8 KB
- system-design/refs/anti-patterns-circular-dependencies.md 5.2 KB
- system-design/refs/anti-patterns-feature-envy.md 3.2 KB
- system-design/refs/anti-patterns-god-object.md 5.1 KB
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.
- 8d ago First seen · 197 lines · 285 tokens per session scan A a4c2a493b174
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.
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.
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.
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…
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.
cleanup-code-inspections
Reduce technical debt and improve code quality by systematically resolving static analysis warnings.
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.