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 traffic-change-diagnosisgit 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/traffic-change-diagnosis)<a href="https://agentmods.dev/skills/clamp-sh/analytics-skills/traffic-change-diagnosis"><img src="https://agentmods.dev/badge/skills/clamp-sh/analytics-skills/traffic-change-diagnosis/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/clamp-sh/analytics-skills/traffic-change-diagnosis"><img src="https://agentmods.dev/badge/skills/clamp-sh/analytics-skills/traffic-change-diagnosis.svg" alt="Reviewed on agentmods" width="80" 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.00088 | $0.03570 |
| Opus 5 | $0.00044 | $0.01785 |
| Sonnet 5 | $0.00018 | $0.00714 |
| Haiku 4.5 | $0.00009 | $0.00357 |
Grade A, and why
traffic-change-diagnosis scanned grade A with 1 finding 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Add a post-deploy smoke test: `curl -s <blog page> | grep <analytics How it starts
The opening of the file, as written. The whole thing — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Traffic change diagnosis
The specialist version of the diagnostic method, applied to one question: why did traffic (sessions, pageviews, unique visitors) move?
Read analytics-diagnostic-method first if you haven't. This skill assumes you already know MECE, triangulation, sample size, and Pyramid presentation. It adds the traffic-specific fingerprints and drill paths.
Opening moves
- Read
analytics-profile.mdif present. The profile tells you the expected monthly traffic range and known measurement gaps. Both matter: a "spike" from 200 to 400 sessions/day on a <1k/month site is plausibly random; the same shape on a 1M/month site is an event. - Restate the question precisely. "Traffic dropped" is not a question. "Daily sessions fell from ~1,400 to ~900 starting April 18, with no corresponding drop in pageviews" is.
- Decide: is this a real change at all? Apply the sample-size rule from
analytics-diagnostic-method. Below ~300 observations per bucket, most "changes" are noise.
The hypothesis tree for traffic
Walk in this order. Cheap checks first.
Traffic change
├── 1. Measurement (check first, always)
│ ├── Tracking regression (script missing, container unpublished, CSP block)
│ ├── Bot filter toggle (inclusion/exclusion changed)
│ └── Attribution shift (referrer policy, cookie policy, cross-domain)
├── 2. Time shape (what does the curve look like?)
│ ├── Cliff (single hour/day step) → discrete event
│ ├── Ramp (gradual over days/weeks) → campaign / SEO / decay
│ ├── Spike (single-day anomaly) → bot burst, viral, outage resolved
│ └── Cyclic (weekly/monthly pattern change) → seasonality, campaign cadence
├── 3. Channel
│ ├── One channel moved → campaign / algo / platform change
│ ├── All channels moved proportionally → measurement or site-wide issue
│ └── One channel grew, another shrank → mix shift (use Simpson's check)
├── 4. Cohort
│ ├── New users changed, returning didn't → acquisition-side change
│ ├── Returning changed, new didn't → retention / email / loyalty change
│ └── Both changed → site-wide or measurement
└── 5. Content / page
├── One page moved → deploy, SEO page, content change
├── Many pages moved proportionally → site-wide (nav, header, domain)
└── Entry pages moved, deep pages didn't → acquisition landing change
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.
- 11d ago First seen · 285 lines · 88 tokens per session scan A 780aac200ef2
traffic-change-diagnosis is a skill published in the GitHub repository clamp-sh/analytics-skills (8 stars, last pushed 3mo ago), licensed MIT. It adds 88 tokens to every session and 3,570 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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-execute
Work through a project's whole backlog: prioritize every task, execute each via a sub-agent, commit after each. Use when the user wants the entire backlog processed ("work through my backlog"), not one named task. Delegates all implementation to sub-agents; clarifies ambiguity by asking the user rather than guessing.