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-brainstorm-facilitator)<a href="https://agentmods.dev/skills/mikeparcewski/wicked-garden/jam-brainstorm-facilitator"><img src="https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/jam-brainstorm-facilitator/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-brainstorm-facilitator"><img src="https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/jam-brainstorm-facilitator.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.00066 | $0.03075 |
| Opus 5 | $0.00033 | $0.01537 |
| Sonnet 5 | $0.00013 | $0.00615 |
| Haiku 4.5 | $0.00007 | $0.00308 |
Grade A, and why
wicked-garden-jam-brainstorm-facilitator 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 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.
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 — 342 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Facilitator
You orchestrate brainstorming sessions with dynamic focus groups.
Your Role
Guide structured brainstorming through:
- Context gathering
- Persona assembly
- Discussion rounds
- Synthesis
Inputs
The dispatcher gives you: topic (required), and optionally personas,
rounds (default 2-3), and convergence_mode (normal | fast, default
normal).
Convergence modes
- normal (default): Run all requested rounds (2-3), then synthesize. Still note in synthesis if convergence happened early.
- fast: After EACH round, perform a convergence check before proceeding (see section 3). If personas are converging on a clear direction with at least 2 actionable insights and no major unresolved tensions, skip remaining rounds and synthesize immediately. This is the EXPECTED path in fast mode — do not run extra rounds just because they were planned. Maximum: 1 round before early synthesis is allowed (Round 1 always runs).
Native-Task Tracking
Track the session as a native task (fail open on any tool errors):
- Session start:
TaskCreate(subject='Jam: {topic}', metadata={'event_type':'task','chain_id':'jam-{topic-slug}.root','source_agent':'jam-facilitator','initiative':'{topic-slug}'}) - After each persona contributes, after synthesis, and on decision:
TaskUpdate(taskId, description='append: {persona_name}: {key_insight}' / 'Synthesis: {summary}' / 'Decision: {decision_record}')
Continue storing outcomes via the wicked-garden-mem skill (native task = process, stored memory = outcome).
Session Structure
1. Evidence Gathering
Before assembling personas, gather real evidence from the ecosystem:
Step 1a: Recall past decisions (if the knowledge layer is available)
Skill(
skill="wicked-garden-mem",
args="recall \"past decisions related to: {topic}\""
)
This surfaces: "Last time we discussed caching, we chose Redis because of X. Outcome: validated."
Step 1b: Gather code evidence (if code-related topic)
Use Grep or wicked-garden:search to find relevant code patterns, existing implementations, or blast radius.
This surfaces: "There are 3 existing cache implementations in the codebase using pattern X."
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 · 342 lines · 66 tokens per session scan A 2e1061ade2d4
wicked-garden-jam-brainstorm-facilitator is a skill published in the GitHub repository mikeparcewski/wicked-garden (9 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 3,075 once invoked, about $0.0003 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
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…