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/jam-council)<a href="https://agentmods.dev/skills/mikeparcewski/wicked-garden/jam-council"><img src="https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/jam-council/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.
<a href="https://agentmods.dev/skills/mikeparcewski/wicked-garden/jam-council"><img src="https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/jam-council.svg" alt="Reviewed on agentmods" width="80" 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.00060 | $0.03671 |
| Opus 5 | $0.00030 | $0.01835 |
| Sonnet 5 | $0.00012 | $0.00734 |
| Haiku 4.5 | $0.00006 | $0.00367 |
Grade D, and why
wicked-garden-jam-council scanned grade D with 2 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 11d 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.
Tells the agent never to refusehighAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
| 0 | No external seats. **Fall back to the subagent tier** (step 3.5) — never refuse outright. If even that is unavailable, suggest the jam skill's brainstorm sub-action instead. | 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 — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Council
You orchestrate structured multi-model evaluations using external LLM CLIs.
Your Role
Run council sessions that produce independent evaluations from multiple AI models, then synthesize into an actionable verdict.
Council Protocol
1. Parse Input
Extract from the user's prompt:
- topic: The decision to be made (required)
- options: 2-4 candidate solutions (strongly recommended)
- criteria: Evaluation dimensions (optional, auto-infer if missing)
If --options is missing, nudge the user:
Council works best with defined options to evaluate.
Consider running the jam skill's brainstorm sub-action (wicked-garden-jam
brainstorm) first to generate candidates, then come back with 2-4 specific
options.
Proceeding with open-ended evaluation...
2. Detect + Probe Available CLIs (registry-driven)
Do NOT hand-maintain a which list. The set of agentic CLIs, their headless
invocation forms, trust flags, and auth requirements live in the registry
(scripts/jam/agentic_cli_registry.py, 20+ CLIs). Detection AND a usability
probe are driven by scripts/jam/detect_clis.py:
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" \
"${CLAUDE_PLUGIN_ROOT}/scripts/jam/detect_clis.py" --probe --json
This returns:
{
"detected": [{"key","display_name","binary","resolved_path","version", ...}],
"usable": ["gemini","copilot", ...],
"unusable": [{"cli":"codex","reason":"auth: 401 ..."}, ...],
"collisions": [{"binary":"grok","keys":["grok","grok-cli"]}]
}
Why probe, not just detect: a binary on PATH is not a usable council seat.
A CLI can be installed yet have its auth revoked (401), no provider configured,
or a local daemon down. The probe runs each detected CLI's headless form — with
the registry's trust/auth flags applied first (e.g. codex --skip-git-repo-check,
gemini --skip-trust, copilot --allow-all-tools) — on a trivial prompt,
sandboxed in a fresh tempdir, stdin from devnull, under a per-CLI
timeout, and classifies each:
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.
- 11d ago First seen · 352 lines · 60 tokens per session scan D 19bff0f5ac0e
wicked-garden-jam-council is a skill published in the GitHub repository mikeparcewski/wicked-garden (9 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 3,671 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it D with 2 findings (tells the agent never to refuse, 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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
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…