What is monitoring-a-wizard-release?

A release-monitoring plan for a wizard or context mill, based on PostHog event data. PostHog is a service that records product events, and the plan compares a new version with the previous one.

Use it to monitor runs started, run duration, language-model cost, completion rate, and success, cancellation, or error outcomes. It also defines useful filters and comparisons by version, program, environment, and model.

It gives the team specific measurements and regression limits to check before and after release. This makes problems in usage, speed, cost, completion, or outcomes easier to spot.

How PostHog/wizard configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to PostHog/wizard. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/PostHog/wizard/main/.claude/skills/monitoring-a-wizard-release/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/PostHog/wizard

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/posthog/wizard/monitoring-a-wizard-release/github.svg)](https://agentmods.dev/skills/posthog/wizard/monitoring-a-wizard-release)

Your own site

<a href="https://agentmods.dev/skills/posthog/wizard/monitoring-a-wizard-release"><img src="https://agentmods.dev/badge/skills/posthog/wizard/monitoring-a-wizard-release/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/posthog/wizard/monitoring-a-wizard-release"><img src="https://agentmods.dev/badge/skills/posthog/wizard/monitoring-a-wizard-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,492 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00055	$0.02492
Opus 5.5	$0.00022	$0.00997
Sonnet 5.5	$0.00011	$0.00498
Haiku 4.5	$0.00006	$0.00249

Measured 16d ago against content hash 335e9e58403a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

monitoring-a-wizard-release 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 16d 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.

.claude/skills/monitoring-a-wizard-release/SKILL.md · 169 lines

How it starts

The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Monitoring a wizard release

Write the plan before you test the release candidate. Post it on the release PR. Then check it after the merge.

The plan

For each metric, write the insight you will watch, the baseline from the previous version, and the change that counts as a regression. Cover these five:

Usage. Runs started per program.
Run duration. p50 and p90 wall clock per run.
Cost. LLM cost per run.
Completion rate. Runs started that finish with status = success.
Outcomes. Success, cancelled, and error, with errors split by error code.

Split each one by version. Also split by program_id, harness, and model when the release touches them.

Filters for every query

build = prod. Other values are dev, ci, and headless.
Person email does not contain @posthog.com.
program_id when the release touches one program.

Key events

All of these fired in the last 14 days. Every wizard event carries run_id, version, build, run_surface, program_id, and command.

Event	Use it for	Properties that matter
`wizard: started`	Runs started	`program_id`, `version`, `run_id`
`wizard: auth complete`	Runs past login	`program_id`, `version`
`wizard: switchboard resolved`	Runner choice per run	`harness` (`pi`, `anthropic`), `sequence` (`orchestrator`, `linear`), `model`
`setup wizard finished`	The one terminal event	`status` (`success`, `cancelled`, `error`), `run_phase`
`wizard: orchestrator run finished`	Orchestrator run shape	`total_duration_ms`, `tasks_total`, `tasks_failed`, `retried_task_count`
`wizard: orchestrator task failed`	Failed tasks	`type` (task type), `error`
`wizard: agent aborted`	Aborted runs	`failure_mode`, `duration_seconds`
`$exception`	Failures by code	`error_code` (`PHW_*`, see error catalog)
`$ai_generation`	LLM cost	`$ai_total_cost_usd`, `$ai_product` (`wizard:<program>`), `run_id`
`wizard: mcp complete`	MCP install after the run	`mcp_outcome`, `mcp_newly_installed_clients`, `mcp_already_installed_clients`, `mcp_failed_clients`, `version`

Read the full file on GitHub · 169 lines

Changes

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.

16d ago Changed · +8 lines 335e9e58403a
20d ago First seen · 161 lines · 55 tokens per session scan A 4fb7b2e54fdd

Subscribe to this mod's changes

monitoring-a-wizard-release is a skill published in the GitHub repository PostHog/wizard (201 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 2,492 once invoked, about $0.0002 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-10-17.

Analytics and metrics onboarding posthog wizard

monitoring-a-wizard-release next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
monitoring-a-wizard-releasePostHog/wizard	Skill	201	yesterday	MIT	A	55	Claude Code
cep-wizardlinkpranay-ai/context-engineering-protocol	Skill	10	1mo ago	Apache-2.0	A	168	Claude Code, Codex
suanfish-design-systemSuanFishXYY/suanfish-design-system	Skill	8	4mo ago	none	A	293	Claude Code, Codex
analytics-productsickn33/agentic-awesome-skills	Skill	49k	yesterday	MIT	A	35	Claude Code
cudaq-guideNVIDIA/skills	Skill	3.9k	yesterday	Apache-2.0	A	26	Claude Code, Codex
cudaq-guideNVIDIA/cuda-quantum	Skill	1.2k	yesterday	Apache-2.0	A	26	Claude Code, Codex
hr-onboardingnexu-io/html-anything	Skill	9.4k	24d ago	Apache-2.0	A	21	Claude Code, Codex

wizard: Skill for Claude Code