Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add mikeparcewski/wicked-garden --skill qe-incident-to-scenario-synthesizergit clone --depth 1 https://github.com/mikeparcewski/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/qe-incident-to-scenario-synthesizer)<a href="https://agentmods.dev/skills/mikeparcewski/wicked-garden/qe-incident-to-scenario-synthesizer"><img src="https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/qe-incident-to-scenario-synthesizer/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/qe-incident-to-scenario-synthesizer"><img src="https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/qe-incident-to-scenario-synthesizer.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.00166 | $0.02676 |
| Opus 5.5 | $0.00066 | $0.01070 |
| Sonnet 5.5 | $0.00033 | $0.00535 |
| Haiku 4.5 | $0.00017 | $0.00268 |
Grade A, and why
wicked-garden-qe-incident-to-scenario-synthesizer scanned grade A 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 20d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- An HTTP request or curl example (fenced block tagged `http` or `curl`). How it starts
The opening of the file, as written. The whole thing — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident-to-Scenario Synthesizer
A prod incident is a free test case — nature already generated the input. You extract it and lock it down as a reproducible scenario. You never mark the scenario active; a human always verifies that the reproducer actually reproduces before it joins the regression suite.
Runtime
Script-backed steps use the wicked-garden launcher: wicked-garden run <plugin-root-relative path, e.g. scripts/…> [args]. It is on PATH after npm i -g wicked-garden; otherwise use npx wicked-garden run …; inside a wicked-crew run it is "$WICKED_GARDEN_ROOT/scripts/wicked-garden".
If none of these is available, or Python 3 is missing, skip the script-backed step, say so, and follow the manual alternative where one is given next to it — never invent the script's output.
Relative paths in this skill are relative to the directory that contains this SKILL.md.
1. Inputs
Accept either path A (incident report) OR path B (direct fields). Reject if neither is provided.
Path A — incident-report markdown
# input
incident_report: docs/postmortems/INC-4829.md
incident_id: INC-4829 # optional; inferred from filename if omitted
The report is expected to contain, at minimum:
- A stack trace (fenced code block tagged
stackortraceback). - An HTTP request or curl example (fenced block tagged
httporcurl). - An "affected endpoint" line matching
^(endpoint|route|path):. - An error class line:
error: <Exception or message>.
Path B — direct fields
# input
incident_id: INC-4829
stack_trace: |
TypeError: Cannot read property 'amount' of undefined
at applyCoupon (/app/src/pricing/coupon.ts:42:15)
at Checkout.finalize (/app/src/checkout.ts:188:7)
endpoint: POST /api/checkout
request_body: { "cart_id": "c_abc", "coupon": "SAVE10" }
expected_error_class: TypeError
run_id— UUID of the currentrunsrow; definesEVIDENCE_DIR..wicked-qe/config.json— optional; used to pick the default test framework for the synthesized steps.- Scenario output dir —
scenarios/. Must exist. One file per incident id.
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.
- 20d ago Changed · +2 lines 08b4b37e436d
- 1mo ago Changed · -15 lines · -128 tokens per session 0308a4ebfece
- 1mo ago Changed · +7 lines fd0b68e5196e
- 1mo ago First seen · 289 lines · 294 tokens per session scan A 7e5b192c5ac8
wicked-garden-qe-incident-to-scenario-synthesizer is a skill published in the GitHub repository mikeparcewski/wicked-garden (9 stars, last pushed yesterday), licensed MIT. It adds 166 tokens to every session and 2,676 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
test-runner
Use this skill when orchestrating agentic end-to-end tests. Resolves target + profile, dispatches the right driver(s) (playwright for web today, peekaboo for macOS (issue #381)), invokes the ux-evaluator agent (opus, read-only) against driver artifacts, reconciles findings with the open issue tracker via…
runtime-verification
Verify code works at runtime through build verification (mandatory), LSP diagnostics, ad-hoc verification for projects without frameworks, E2E and smoke tests, and visual verification (screenshot-analyze-verify for UI changes). Skip whitelist strictly enforced (markdown-only, config-only, dependency-bump-only with…
eval-integration
Specialized integration evaluator for the Evaluate-Loop. Use this for evaluating tracks that integrate external services — Supabase auth/DB, Stripe payments, Gemini API, third-party APIs. Checks API contracts, auth flows, data persistence, error recovery, environment config, and end-to-end flow integrity. Dispatched…
browser-test-self-healing
Build an AgentWorks workflow that diagnoses a browser-test failure, proposes a test-only repair, verifies it in isolation, obtains the configured review, and updates canonical tests and application knowledge. Use for stale or flaky browser automation, not product defects.
flaky-test-detection-stabilization
Build AgentWorks browser-test flake detection and reviewed stabilization using repeated isolated attempts and evidence comparison. Use when identical test inputs produce inconsistent outcomes.
parallel-gate-legs-killed-for-memory-count-cannot-see-ram
Two sessions run local test legs on the same machine and one session's leg is killed for memory mid-run, while the concurrency guard everybody uses — a count of running test processes — reads well inside its limit the whole time. Use when: (1) a background test run ends with a harness notice like "stopped because the…