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-profile-setupgit 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-profile-setup)<a href="https://agentmods.dev/skills/clamp-sh/analytics-skills/analytics-profile-setup"><img src="https://agentmods.dev/badge/skills/clamp-sh/analytics-skills/analytics-profile-setup/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/analytics-profile-setup"><img src="https://agentmods.dev/badge/skills/clamp-sh/analytics-skills/analytics-profile-setup.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.00060 | $0.03321 |
| Opus 5 | $0.00030 | $0.01661 |
| Sonnet 5 | $0.00012 | $0.00664 |
| Haiku 4.5 | $0.00006 | $0.00332 |
Grade A, and why
analytics-profile-setup 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 8d 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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analytics profile setup
What this skill does
Produces a single file, analytics-profile.md, in the repo root. The file captures the handful of facts every other analytics skill needs to stop giving generic advice:
- Industry and business model (B2B SaaS, B2C subscription, ecommerce, lead-gen, content/ads, marketplace)
- Primary conversion event
- Rough traffic volume (sets sample-size expectations)
- ICP / target persona
- Pricing model (what LTV and CAC even mean for them)
- Data stack (which analytics tool, which events are tracked, known gaps)
- Known measurement quirks (bot filters on or off, UTM conventions, cross-domain tracking)
Downstream skills (analytics-diagnostic-method, traffic-change-diagnosis, channel-and-funnel-quality, metric-context-and-benchmarks) open by checking for this file. If it exists, they pull their defaults from it. If it doesn't, they fall back to generic cross-industry assumptions and prompt the user to run this skill.
When NOT to run this
- The user is asking a one-off question and doesn't want ceremony. Answer the question; don't volunteer the setup.
- A profile already exists and is less than ~6 months old. Re-running overwrites useful context. Only re-run if the user explicitly asks, or the business has materially changed.
Method
Five phases. Keep it tight: the whole thing should take the user 5 minutes.
Phase 1. Check for an existing profile
ls analytics-profile.md
If it exists:
- Read it.
- Summarize what's already captured in 3-5 bullet points.
- Ask: "Do you want to (a) keep it as-is, (b) update specific fields, or (c) regenerate from scratch?"
Don't just overwrite. A stale profile is usually 80% still correct.
Phase 2. The interview
Ask one question at a time. Wait for the answer. Do not batch-ask. Agents that dump 8 questions at once get fragmented replies and force the user to re-read the whole block.
Use this question order. The reasoning for each question is in parentheses so the agent knows why it matters and can adapt phrasing if the user gives a partial answer.
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.
- 8d ago First seen · 260 lines · 60 tokens per session scan A ece6be7d3362
analytics-profile-setup is a skill published in the GitHub repository clamp-sh/analytics-skills (8 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 3,321 once invoked, about $0.0003 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…