summarizing-posthog-analytics

summarizing-posthog-analytics is a skill for Claude Code, Codex from Tracer-Cloud/opensre. It costs 53 tokens per session (1,195 once invoked), scanned A, original, Apache-2.0.

A reporting workflow that reads PostHog, a product-analytics service, and turns event data into a summary for each metric over a chosen time period.

In plain words
What is it for?
Use it for weekly product-analytics updates, usage overviews, metric summaries, and reports about what happened during a period.
Why use it?
It replaces a raw dashboard export with a concise account of what changed and why it matters, while checking that the requested data fields exist.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it for weekly product-analytics updates, usage overviews, metric summaries, and reports about what happened during a period.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tracer-cloud/opensre/summarizing-posthog-analytics
About the project

OpenSRE is an open-source framework for building AI agents that investigate and resolve production incidents using operational data and tools. It is for site reliability engineers who want customizable incident-response workflows, training, and evaluation on their own infrastructure.

Tracer-Cloud/opensre · 11,969 stars · on GitHub · discord.com

Install

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.

Any agent
npx skills add Tracer-Cloud/opensre --skill summarizing-posthog-analytics
Clone the repo
git clone --depth 1 https://github.com/Tracer-Cloud/opensre

Made for: Claude Code, Codex.

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.

agentmods badge for summarizing-posthog-analytics

README.md
[![agentmods](https://agentmods.dev/badge/skills/tracer-cloud/opensre/summarizing-posthog-analytics/github.svg)](https://agentmods.dev/skills/tracer-cloud/opensre/summarizing-posthog-analytics)
Your own site
<a href="https://agentmods.dev/skills/tracer-cloud/opensre/summarizing-posthog-analytics"><img src="https://agentmods.dev/badge/skills/tracer-cloud/opensre/summarizing-posthog-analytics/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.

agentmods 80×15 button for summarizing-posthog-analytics

Your own site · 80×15
<a href="https://agentmods.dev/skills/tracer-cloud/opensre/summarizing-posthog-analytics"><img src="https://agentmods.dev/badge/skills/tracer-cloud/opensre/summarizing-posthog-analytics.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,195 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00053 $0.01195
Opus 5.5 $0.00021 $0.00478
Sonnet 5.5 $0.00011 $0.00239
Haiku 4.5 $0.00005 $0.00120

Measured 1mo ago against content hash 6d17fac65df9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

summarizing-posthog-analytics 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 1mo 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.

integrations/posthog/tools/skills/summarizing-posthog-analytics/SKILL.md · 113 lines

How it starts

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

PostHog Summary

PostHog product-analytics reporting for chat delivery. Produce a per-metric pulse over a window — what moved, why it matters — not a raw dashboard export. Single source (PostHog MCP); finish here, then optionally suggest a multi-source follow-up.

Requires the PostHog MCP integration (posthog_mcp). The REST-only posthog integration cannot serve this skill.

1. Discover

list_posthog_tools once with name_filter: "insights dashboard sql events" to find the query surface. Then call read-data-schema (or the equivalent schema tool) BEFORE any aggregation query and only reference events and properties it confirms exist. Do not reference a property (e.g. properties.$mcp_error) without seeing it in the schema first — HogQL rejects queries against unknown properties. To pull metric data, use call_posthog_tool with tool_name: "execute-sql" and SQL as a top-level string:

{
  "tool_name": "execute-sql",
  "arguments": { "query": "SELECT count() FROM events WHERE event = '$pageview'" }
}

Never nest the SQL ({"query": {"query": "SELECT …"}}) — PostHog rejects that with parameter "query" must be of type string. Use insight/dashboard tools when the user names a specific dashboard.

2. Fetch metrics

Map user words to windows:

  • 24h — "today", "overnight", morning report
  • 7d — "this week", default weekly report
  • 30d — "this month", monthly rollup

Run one small HogQL query per metric — do NOT combine multiple metrics into a single aggregated statement, and never cross-join events against synthetic "window" rows. That combined shape is the most common cause of PostHog's unknown error running this query. Return only aggregate numbers (two columns: current / previous) — never event-level rows. Compute the two windows with an explicit conditional aggregate over a single time filter, e.g.:

SELECT
  countIf(timestamp >= now() - INTERVAL 7 DAY) AS current,
  countIf(timestamp >= now() - INTERVAL 14 DAY
          AND timestamp < now() - INTERVAL 7 DAY) AS previous
FROM events
WHERE event = '$pageview'

Read the full file on GitHub · 113 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.

  1. 1mo ago First seen · 113 lines · 53 tokens per session scan A 6d17fac65df9

Subscribe to this mod's changes

summarizing-posthog-analytics is a skill published in the GitHub repository Tracer-Cloud/opensre (11,969 stars, last pushed today), licensed Apache-2.0. It adds 53 tokens to every session and 1,195 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-09-10.

Related

Other skills, from other repositories

grafana-expert

Expert-level Grafana dashboards, visualization, data sources, alerting, and production operations. Use when the user mentions dashboards, visualization, monitoring, observability, or alerting, or when the task involves Grafana Architecture, Installation on Kubernetes, Data Sources, or Dashboard JSON.

personamanagmentlayer/pcl · 61 tokens

host_bash

A read-only shell skill for examining files and running diagnostic commands in a restricted environment. A shell is a text interface for operating-system commands.

ongridio/ongrid · 26 tokens

host_restart_service

A tool for restarting approved systemd services, which are background programs managed by Linux's service manager.

ongridio/ongrid · 23 tokens

monitoring-expert

Expert-level monitoring and observability with Prometheus, Grafana, logging, and alerting. Use when the user mentions observability, Prometheus, Grafana, logging, metrics, or alerting, or when the task involves The Three Pillars of Observability, Monitoring Fundamentals, Prometheus Configuration, or Alert Rules.

personamanagmentlayer/pcl · 70 tokens

datadog

Full-stack observability with Datadog APM, logs, metrics, synthetics, and RUM. Use when implementing monitoring, tracing, alerting, or cost optimization for production systems.

bobmatnyc/claude-mpm-skills · 43 tokens

grafana

Build operable Grafana dashboards with template variables, provisioning-as-code, and unified alerts wired to Prometheus/Loki; avoid high-cardinality panels agents love to ship.

alivirgo/Major-AI-Skills · 37 tokens