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 gate-benchmark-rebaselinegit 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/gate-benchmark-rebaseline)<a href="https://agentmods.dev/skills/mikeparcewski/wicked-garden/gate-benchmark-rebaseline"><img src="https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/gate-benchmark-rebaseline/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/gate-benchmark-rebaseline"><img src="https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/gate-benchmark-rebaseline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00156 | $0.01384 |
| Opus 5.5 | $0.00062 | $0.00554 |
| Sonnet 5.5 | $0.00031 | $0.00277 |
| Haiku 4.5 | $0.00016 | $0.00138 |
Grade A, and why
wicked-garden-platform-gate-benchmark-rebaseline 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 1mo 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gate-Result Benchmark Re-baseline
Operational procedure for updating tests/crew/benchmark_baseline.json after a legitimate perf change on main.
When to re-baseline
Re-baseline only when a deliberate perf change lands on main. Examples:
- Validator hardening (added / removed gate-result schema checks)
- Cache eviction tuning (changes to gate-result ingestion memoization)
- Schema expansion (new required fields in
gate-result.json) - Sanitizer pattern changes (
scripts/qe/content_sanitizer.py)
Do not re-baseline to silence a regression. If the benchmark fails on a PR that didn't intend perf work, treat it as a real regression and find the cause.
How the lane works
- Workflow:
.github/workflows/benchmark.yml - Trigger: PRs touching
scripts/crew/phase_manager.py, the gate-result schema/sanitizer (scripts/qe/content_sanitizer.py), or the benchmark test/baseline themselves. Other PRs skip the lane to keep default CI cost flat. - Test:
tests/crew/test_gate_result_benchmark.py::test_load_gate_result_p95_within_2x_baseline - Marker:
benchmark— opt-in. Localuv run pytestdeselects it (seepyproject.tomladdopts = "-m 'not benchmark'"). - Explicit invocation:
uv run pytest -m benchmark - Fixtures: 50 deterministic
gate-result.jsonfiles cycling through 1 KB / 4 KB / 16 KB / 60 KB (bounded byMAX_SUMMARY_BYTES). Each round clears the memoization cache so the full validate + sanitize + cache-insert path is measured. Cache-hit timing is not part of the SLO. - Baseline:
tests/crew/benchmark_baseline.json—p95_nsin nanoseconds. - Assertion:
p95_current ≤ slo_multiplier × p95_baseline(defaultslo_multiplier = 2.0). The workflow comments the delta on every triggered PR. - Missing-baseline behavior: if
benchmark_baseline.jsonis deleted or malformed, the test soft-skips with a directive to record one. The SLO is not enforced until a valid baseline is present — so a re-baseline PR can merge without a circular dependency.
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.
- 1mo ago Changed · +2 lines 7553d86aed4e
- 1mo ago First seen · 109 lines · 156 tokens per session scan A 84b03550a631
wicked-garden-platform-gate-benchmark-rebaseline is a skill published in the GitHub repository mikeparcewski/wicked-garden (9 stars, last pushed today), licensed MIT. It adds 156 tokens to every session and 1,384 once invoked, about $0.0006 per session on Opus 5.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-09-03.
Other skills, from other repositories
cloudflare-workers-testing
Comprehensive testing guide for Cloudflare Workers using Vitest and @cloudflare/vitest-pool-workers. Use for test setup, binding mocks (D1/KV/R2/DO), integration tests, or encountering test failures, mock errors, coverage issues.
e2e-automation-project
Maintain a dedicated automation test project per repository - separate from the product's unit tests - with API, worker, and UI suites written scenario-first.
cicd-integration
Generate CI pipeline files and check scripts (GitHub Actions, GitLab, CircleCI, Bitbucket) that automate design system checks: token validation, hardcoded values, a11y scans, visual regression, bundle size. Trigger: set up CI, quality gates, automate these checks. Not for running an audit.
vibe-safe-deploy
Performs deployment with pre-flight checks, atomic replacement, post-deploy verification, provenance (proving the environment serves the exact commit you pushed), and automatic rollback. Use before any deployment to staging, preview, or production.
automation-pipeline-integration
Wire the automation test project into the repository's own pipeline so every task must pass the suite before it can leave QA.
gitlab:ci-monitor
Watch GitLab CI and investigate pipeline failures. Use when a pipeline or job is failing or red, when watching MR CI, branch builds, or a specific pipeline, when waiting for CI to go green, or when authoring or validating .gitlab-ci.yml.