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 PostHog/posthog-foss --skill exploring-mcp-sessionsgit clone --depth 1 https://github.com/PostHog/posthog-fossWrote 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/posthog/posthog-foss/exploring-mcp-sessions)<a href="https://agentmods.dev/skills/posthog/posthog-foss/exploring-mcp-sessions"><img src="https://agentmods.dev/badge/skills/posthog/posthog-foss/exploring-mcp-sessions/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/posthog/posthog-foss/exploring-mcp-sessions"><img src="https://agentmods.dev/badge/skills/posthog/posthog-foss/exploring-mcp-sessions.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.00096 | $0.02118 |
| Opus 5 | $0.00048 | $0.01059 |
| Sonnet 5 | $0.00019 | $0.00424 |
| Haiku 4.5 | $0.00010 | $0.00212 |
Grade A, and why
exploring-mcp-sessions 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- exploring-mcp-sessions — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exploring MCP sessions
An MCP session is one agent run: the set of $mcp_tool_call events sharing a
$session_id, ordered by timestamp.
Listing sessions, reading a session's tool calls, and summarising its goal each
have a typed tool — reach for those first. Drop to HogQL only for the three
things the typed tools genuinely can't do (see
When to drop to SQL). The full $mcp_* property schema
and query recipes live in the shared reference:
models-mcp.md.
Tools
| Tool | Purpose |
|---|---|
posthog:mcp-analytics-sessions-list |
List sessions — one row per session, newest first |
posthog:mcp-analytics-sessions-tool-calls |
One session's tool calls, chronological |
posthog:mcp-analytics-sessions-generate-intent |
LLM summary of a session's goal (cached after first call) |
posthog:execute-sql |
Errored sessions, effective tool names, cross-session cuts |
The three mcp-analytics-* tools are gated behind the mcp-analytics flag and
run the same code as the sessions UI, so results match the screen. If they aren't
in your tool list, the project doesn't have the flag — fall back to
posthog:execute-sql, which is ungated.
The date-window trap — read this first
The two detail tools default to a 7-day lookback. A session you found in a
list that reaches further back will come back empty unless you pass its
session_start as date_from:
posthog:mcp-analytics-sessions-tool-calls—date_fromis an absolute ISO timestamp; pass thesession_startyou got fromposthog:mcp-analytics-sessions-list.posthog:mcp-analytics-sessions-generate-intent— samedate_fromquery param, same reason.
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.
- 9d ago First seen · 191 lines · 96 tokens per session scan A 9ea26041a342
exploring-mcp-sessions is a skill published in the GitHub repository PostHog/posthog-foss (715 stars, last pushed today), licensed MIT. It adds 96 tokens to every session and 2,118 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.