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 agentmods add skills/posthog/wizard/exploring-the-wizardnpx skills add PostHog/wizard --skill exploring-the-wizardgit clone --depth 1 https://github.com/PostHog/wizardWhat 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 | $0.00073 | $0.01766 |
| Opus 5 | $0.00036 | $0.00883 |
| Sonnet 5 | $0.00015 | $0.00353 |
| Haiku 4.5 | $0.00007 | $0.00177 |
Grade A, and why
exploring-the-wizard 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 2d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exploring the wizard as an agent
Drive a real wizard run yourself: boot it on an app, read each screen, decide, act, snapshot.
The MCP server
Everything goes through the wizard-ci MCP server, registered in this
repo's .mcp.json (npx tsx scripts/wizard-ci-mcp.no-jest.ts) — it runs the
wizard from this checkout's source, so whatever branch you're on is what
you're testing. If the tools (open_app, read_state, …) aren't available,
the server isn't approved yet — ask the user to approve wizard-ci, then
retry. For how the harness works underneath, read
e2e-harness/ARCHITECTURE.md.
What it can do
- Boot the real TUI on any app directory and walk every pre-auth screen: framework detection, gatherContext, feature discovery, warehouse scan, intro, setup questions, health check, auth.
- Run the real integration (
run_agent): OAuth-equivalent bootstrap, the full agent run, outro, MCP install, skills — creating real PostHog resources (dashboard + insights) in the target project. - Show you every screen (
render_screen) exactly as a user sees it. - What it can't do: drive two apps at once (
open_appreplaces the active wizard), or advanceauth/runwithout credentials.
Credentials
Two modes — pick by how far the run must go:
- Detection-only (no credentials).
open_appneeds just{ appDir, projectId }. Everything up to and including theauthscreen runs credential-free — enough to regression-test detection, setup questions, and screen flow. End the run atauth. - Full run (credentials required) — anything past
auth, i.e.run_agent. Prompt the user for three things before starting:- Key — ask "What's the path to your phx key file?" and pass it as
keyFile(preferred: keeps the key out of logs). If they hold the key in an environment variable instead, have them write it to a file first (printenv THEIR_VAR > /tmp/phx-key— you never echo it) or passapiKeyinline as a last resort. Never print or commit the key. - Project id — the PostHog project the key is scoped to (
projectId). - Region —
us(default) oreu(region).
- Key — ask "What's the path to your phx key file?" and pass it as
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.
- 2d ago First seen · 136 lines · 73 tokens per session scan A 4bbc27f8c7b7
exploring-the-wizard is a skill published in the GitHub repository PostHog/wizard (190 stars, last pushed 3d ago), licensed MIT. It adds 73 tokens to every session and 1,766 once invoked, about $0.0004 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-30.
Other skills, from other repositories
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
e2e-deployment-skill
Use this deployment skill to verify shared skills load during Playwright startup.
launch
Launch Code OSS (VS Code from sources) into an isolated throwaway profile with unique debug ports so you can drive it with @playwright/cli AND attach a Node debugger via dap-cli in the same session. Use when working on VS Code itself and you want to interact with the running workbench, automate chat or UI flows, test…
playwright-screen-recording
Record browser test videos with Playwright for PR review and bug fix verification.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
actionbook-web-test
Run browser-based web tests against websites using Actionbook CLI. Activate when the user wants to test a website workflow, run smoke tests, verify a user flow, check if a web application works, run regression tests, or validate browser-based interactions. Supports test definition, execution, assertion, reporting, and…