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/mixpanel/ai-plugins/analyze-reportnpx skills add mixpanel/ai-plugins --skill analyze-reportgit clone --depth 1 https://github.com/mixpanel/ai-pluginsWrote 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/mixpanel/ai-plugins/analyze-report)<a href="https://agentmods.dev/skills/mixpanel/ai-plugins/analyze-report"><img src="https://agentmods.dev/badge/skills/mixpanel/ai-plugins/analyze-report.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 | $0.00218 | $0.02054 |
| Opus 5 | $0.00109 | $0.01027 |
| Sonnet 5 | $0.00044 | $0.00411 |
| Haiku 4.5 | $0.00022 | $0.00205 |
Grade A, and why
analyze-report 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 4d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mixpanel Analyze Report
Engine required — resolve an engine per
ENGINE.md: one named in the conversation or loaded instructions is mandatory (not set up → offer/mixpanel:installfor it); otherwise use the Mixpanel MCP server, or offer/mixpanel:installif it's unavailable.
Take a Mixpanel report or chart that already exists (or just got built) and turn it into a one-screen summary the customer can act on. The skill is lean by default — it explains what the report shows and flags what's notable, but does not chase root causes unless the customer asks.
This skill is built for fast interpretation: flag what you see and stop. The boundary — when a "why" question turns this into a root-cause investigation — is defined in "Hybrid scope — when to stop" below.
When this skill runs, it does four things in order
- Locate the report — by URL, ID, or fresh build
- Pull the data — re-run the query and parse the result
- Read the shape — trend, anomalies, breakdown distribution
- Summarize for the customer — what it shows, what's notable, what to do next
Step 1 — Locate the report
Three input modes. Detect which one applies from the customer's message:
Mode A — Customer provides a URL or chart/report ID
Most common. Mixpanel report URLs look like https://mixpanel.com/project/<project_id>/view/<board_id>/app/<chart> or include report_id=<id>. Extract the ID(s).
Fetch the report's saved configuration — the events, properties, filters, breakdowns, date range, and chart type — so you can ground the analysis without asking the customer to re-explain what they built.
If you can't resolve the URL/ID (404, permission error, malformed URL), say so plainly and ask if they meant a different report.
Mode B — Customer describes the report in natural language
If the customer says "the DAU chart on my exec board" or "the funnel I built last week," they're pointing at an existing report but haven't given an ID. Search saved reports for candidates, show the top 3 matches with their titles and dates, and ask which one they mean.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 198 lines · 218 tokens per session scan A 302f57e40a13
analyze-report is a skill published in the GitHub repository mixpanel/ai-plugins (15 stars, last pushed today), licensed Apache-2.0. It adds 218 tokens to every session and 2,054 once invoked, about $0.0011 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…