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/classify)<a href="https://agentmods.dev/skills/mikeparcewski/wicked-garden/classify"><img src="https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/classify.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.00116 | $0.02023 |
| Opus 5 | $0.00058 | $0.01012 |
| Sonnet 5 | $0.00023 | $0.00405 |
| Haiku 4.5 | $0.00012 | $0.00202 |
Grade B, and why
wicked-garden-classify scanned grade B with 1 finding 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 7d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
allowed-tools: ["*"] How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wicked-garden:classify
You are classifying a prompt into a v11 work-shape archetype. Your output drives downstream archetype routing for the rest of the session (until the user changes scope or invokes this skill again).
Why this exists
The v11 hook auto-classifier is a regex + boolean-signal heuristic. It works for prompts whose vocabulary matches the catalog phrase lists, but it misses paraphrases and underuses signals. You are a better classifier than regex. This skill is the path to use the model's full reasoning on the classification step, then persist the result so the rest of the session benefits without re-running classification on every turn.
Routing model (council-is-the-router)
This skill is the session router. The former wicked-signals product (a
separate text-in / intent-out classifier) was archived because intent /
work-shape classification is a native model capability — the router is just a
model reading the prompt with full tool access (allowed-tools: ["*"]), which
is exactly this skill. Read it as one council member making the routing call on
the fast path.
When a routing or decision call is genuinely hard, ambiguous, or high-stakes,
escalate to the multi-model council (wicked-garden-jam → council, worker
wicked-garden-jam-council): multiple independent models deliberate, still with
garden tools for additional processing. The council is the escalation, not a
per-prompt router — convening 20 CLIs on every prompt would be absurd cost.
- Fast path (always on) — the
prompt_submithook emits<wg classify-due />, you classify + persist here, the parent turn steers on the persisted archetype. - Escalation (on demand) —
wicked-garden-jam council <question> --options "…".
What the catalog declares
.claude-plugin/archetypes.json defines the work-shape archetypes. Read it
once at the start of this skill. Summary table:
| Archetype | Phases | Use when |
|---|---|---|
| triage | classify | prompt is genuinely ambiguous; ask for clarification |
| explore | frame → diverge → converge | open problem space, multiple paths, brainstorm |
| specify | elicit → structure → validate | requirements / acceptance criteria need writing |
| decide | brief → options → score → record | 2+ viable options, need an ADR |
| ship | canary → ramp → full → soak | already-built change being rolled out |
| review | scope → assess → findings → remediate-or-accept | independent assessment of an artifact |
| incident | triage → investigate → mitigate → resolve → followup | live production failure |
| build | plan → implement → test → review | implement a feature or fix (most common) |
| migrate | plan → expand → backfill → cutover → contract | in-place shape change with rollback proof |
| modernize | discover → extract → blueprint → transform → parity → cutover | port a legacy codebase to a new stack (NOT in-place) |
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.
- 7d ago First seen · 181 lines · 116 tokens per session scan B 67e14cb9d9b3
wicked-garden-classify is a skill published in the GitHub repository mikeparcewski/wicked-garden (9 stars, last pushed 2d ago), licensed MIT. It adds 116 tokens to every session and 2,023 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…