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/stuartbrameld/posthog-mcp/claude-mdgit clone --depth 1 https://github.com/stuartbrameld/posthog-mcpWrote 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/instructions/stuartbrameld/posthog-mcp/claude-md)<a href="https://agentmods.dev/instructions/stuartbrameld/posthog-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/stuartbrameld/posthog-mcp/claude-md.svg" alt="Measured on agentmods" 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.01242 | $0.01242 |
| Opus 5 | $0.00621 | $0.00621 |
| Sonnet 5 | $0.00248 | $0.00248 |
| Haiku 4.5 | $0.00124 | $0.00124 |
Grade A, and why
posthog-mcp 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 5d 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.
This is a copy
94% identical to mcp CLAUDE.md — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Development Commands
pnpm run dev- Start development server using Wranglerpnpm run deploy- Deploy to Cloudflare Workerspnpm run format- Format code using Biomepnpm run lint:fix- Lint and fix code using Biomepnpm run schema:build:json- Generate JSON schema from Zod schemas for Python/other language implementationswrangler types- Generate TypeScript types for Cloudflare Workers
Code Architecture
This is a PostHog MCP (Model Context Protocol) server built on Cloudflare Workers that provides API access to PostHog analytics data. The server acts as a bridge between MCP clients (like Claude Desktop, Cursor, Windsurf) and PostHog's API.
Project Structure
The repository is organized to support multiple language implementations:
mcp/
├── typescript/ # TypeScript implementation
│ ├── src/ # TypeScript source code
│ ├── tests/ # TypeScript tests
│ └── scripts/ # TypeScript build scripts
├── python/ # Python implementation (planned)
├── schema/ # Shared schema files for all implementations
│ └── tool-inputs.json # Generated JSON schema for cross-language compatibility
├── biome.json # Shared code formatting configuration
└── CLAUDE.md # Project documentation
Key Components (TypeScript Implementation)
- Main MCP Class (
typescript/src/index.ts):MyMCPextendsMcpAgentand defines all available tools for interacting with PostHog - Unified API Client (
typescript/src/api/client.ts):ApiClientclass provides type-safe methods for all PostHog API interactions with proper error handling and schema validation - Schema Validation (
typescript/src/schema/): Zod schemas for validating API requests and responses - Tool Input Schemas (
typescript/src/schema/tool-inputs.ts): Centralized Zod schemas for all MCP tool inputs, exported toschema/tool-inputs.jsonfor other language implementations - Caching (
typescript/src/lib/utils/cache/): User-scoped memory cache for storing project/org state - Documentation Search (
typescript/src/inkeepApi.ts): Integration with Inkeep for PostHog docs search - Utility Functions (
typescript/src/lib/utils/api.ts): Helper functions for pagination and URL generation
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.
- 5d ago First seen · 102 lines · 1,242 tokens per session scan A 512d47a72a37
posthog-mcp CLAUDE.md is an instructions file published in the GitHub repository stuartbrameld/posthog-mcp (1 stars, last pushed 1y ago), licensed MIT. It adds 1,242 tokens to every session, about $0.0062 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to mcp CLAUDE.md, differing in 2 lines, and is treated as a copy.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.