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 instructions/posthog/wizard/claude-mdgit 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.00046 | $0.00046 |
| Opus 5 | $0.00023 | $0.00023 |
| Sonnet 5 | $0.00009 | $0.00009 |
| Haiku 4.5 | $0.00005 | $0.00005 |
Grade A, and why
wizard CLAUDE.md 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.
What it actually says
CLAUDE.md
Repo guidance for all agents lives in AGENTS.md — the single source of truth. It's imported below so Claude Code picks it up automatically.
@AGENTS.md
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 · 7 lines · 46 tokens per session scan A 31e8f5299e5e
wizard CLAUDE.md is an instructions file published in the GitHub repository PostHog/wizard (190 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session, about $0.0002 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 instructions, from other repositories
claude-for-designers CLAUDE.md
Instructions for mshadmanrahman/claude-for-designers, covering claude for designers: how to work in this folder, what this folder is, when the student asks about the folder, orient them, work out which class they are on before you answer and answer keys: never open one unasked.
posthog.com AGENTS.md
AGENTS.md instructions for PostHog/posthog.com, covering agents.md, making changes, prs, content prs and before you open a pr.
posthog.com CLAUDE.md
Claude Code instructions for PostHog/posthog.com, a project described as: Official docs, website, and handbook for PostHog.
solana-uiux-onboarding-kit CLAUDE.md
Instructions for draaujpeg/solana-uiux-onboarding-kit, covering solana ui/ux onboarding kit, language, where the truth lives, commands and always.
mcp CLAUDE.md
Instructions for PostHog/mcp, covering claude.md, development commands, code architecture, project structure and key components (typescript implementation).
survey-mcp-server AGENTS.md
Instructions for cyanheads/survey-mcp-server, covering agent protocol & architectural mandate, i. core principles (non‑negotiable), ii. architectural overview & directory structure, iii. architectural philosophy: pragmatic solid and iv. tool development workflow.