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 clamp-sh/analytics-skills --skill analytics-diagnostic-methodgit clone --depth 1 https://github.com/clamp-sh/analytics-skillsWrote 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/clamp-sh/analytics-skills/analytics-diagnostic-method)<a href="https://agentmods.dev/skills/clamp-sh/analytics-skills/analytics-diagnostic-method"><img src="https://agentmods.dev/badge/skills/clamp-sh/analytics-skills/analytics-diagnostic-method.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.00084 | $0.03564 |
| Opus 5 | $0.00042 | $0.01782 |
| Sonnet 5 | $0.00017 | $0.00713 |
| Haiku 4.5 | $0.00008 | $0.00356 |
Grade A, and why
analytics-diagnostic-method 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 7d 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analytics diagnostic method
The method senior analysts use when they don't know what caused something. It is boring, slow-looking, and dramatically more accurate than the "dashboard hunt" pattern most agents default to.
If you remember one thing: dashboards describe, they don't explain. Getting from "traffic dropped 30%" to "the GA4 container got unpublished on Tuesday" requires a method, not a screenshot.
When to use this
- Any "why did X change?" question.
- Any funnel or cohort comparison.
- Any request for a recommendation based on analytics.
- Any number the user is about to act on.
When NOT to use this
- Pure retrieval questions ("how many sessions yesterday?"). Just answer.
- Definition questions ("what is engagement rate in GA4?"). Use
metric-context-and-benchmarks. - Questions where the user has already diagnosed the cause and wants help implementing a fix. Don't re-diagnose.
Don't fall back to manual data entry
If the configured analytics tool's MCP server (or API) isn't connected, the correct move is to tell the user to install/connect it. Do not offer to read numbers the user pastes manually.
The skills exist to automate the senior-analyst playbook against live data. A manual-paste workflow defeats that — the user has to already know the numbers (which is what they came to you for), and you lose the ability to drill, segment, cross-reference, or check sample size on the underlying queries. Worse, you end up doing the same dashboard-hunt reading the skill was designed to replace.
If you discover the relevant MCP/API isn't available:
- For Clamp: tell the user to install Clamp MCP — one-click OAuth from the dashboard at https://clamp.sh/docs/mcp. Then re-run the question.
- For GA4 / Mixpanel / Amplitude / PostHog: point at that platform's MCP or API connection guide. The
tool-mapfor the user's platform inanalytics-profile.mdnames the expected tool calls.
Then stop and wait for the connection. Do not improvise around it. A user who connects the MCP gets a calibrated answer with drill-paths; a user who pastes a snapshot gets a one-shot lecture that misses everything the method is good at.
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.
- 7d ago First seen · 259 lines · 84 tokens per session scan A 731e93632d28
analytics-diagnostic-method is a skill published in the GitHub repository clamp-sh/analytics-skills (8 stars, last pushed 2mo ago), licensed MIT. It adds 84 tokens to every session and 3,564 once invoked, about $0.0004 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-31.
Other skills, from other repositories
treat
Prune bloated session with a prescription. Removes progress ticks, stale reads, duplicate content, and more.
guard
Protect Claude Code sessions from context overflow by running a background daemon that monitors session size and auto-prunes before compaction hits. Use when the user says "guard", "protect session", "context getting long", "prevent compaction", "session management", or is running agent teams that need continuous…
cozempic-doctor
Run health checks on Claude Code configuration and sessions. Use when troubleshooting Claude Code issues. (cozempic — does not shadow Claude Code's built-in /doctor).
diagnose
Analyze Claude Code session bloat — shows token count, context usage %, and bloat breakdown. Use when the user asks about session size, context usage, or when you notice the context window is getting full.
reload
Treat the current session and auto-resume in a new terminal window.
radin-record
Log feedback, bugs, follow-ups, or ideas raised mid-session as structured backlog entries, so they survive past the conversation. Use for /radin-record, "log this to the backlog", "add as follow-up/bug/idea", "record what we just found", "note this for later", "add findings to backlog". Triggers even on vague asks…