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/arbazkhan971/godmode/analyticsnpx skills add arbazkhan971/godmode --skill analyticsgit clone --depth 1 https://github.com/arbazkhan971/godmodeWrote 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/arbazkhan971/godmode/analytics)<a href="https://agentmods.dev/skills/arbazkhan971/godmode/analytics"><img src="https://agentmods.dev/badge/skills/arbazkhan971/godmode/analytics.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.00031 | $0.02745 |
| Opus 5 | $0.00015 | $0.01373 |
| Sonnet 5 | $0.00006 | $0.00549 |
| Haiku 4.5 | $0.00003 | $0.00275 |
Grade A, and why
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 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 — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analytics — Analytics Implementation
Activate When
- User invokes
/godmode:analytics - User says "add analytics", "track events", "set up tracking"
- User says "create a funnel", "A/B test", "implement experiments"
- User says "add Segment", "set up Amplitude", "configure Mixpanel", "add PostHog"
- User says "privacy-friendly analytics", "GDPR-compliant tracking", "cookieless analytics"
- When building new features that need usage measurement
- When
/godmode:planidentifies analytics instrumentation tasks
Workflow
Step 1: Analytics Strategy Discovery
Understand what needs to be measured and why:
ANALYTICS DISCOVERY:
Project: <name and purpose>
Goals:
- <business goal 1 — e.g., increase conversion rate>
- <business goal 2 — e.g., reduce churn>
- <business goal 3 — e.g., improve feature adoption>
Key questions to answer:
- <question 1 — e.g., "Where do users drop off in onboarding?">
- <question 2 — e.g., "Which features correlate with retention?">
- <question 3 — e.g., "What is our activation rate?">
Platform: <web | mobile | both | server-side>
Framework: <React | Next.js | Vue | React Native | iOS | Android | backend>
Privacy requirements: <GDPR | CCPA | HIPAA | none | strict — no third-party>
Existing analytics: <none | GA4 | Segment | Amplitude | Mixpanel | custom>
Budget: <free tier | startup plan | enterprise>
If the user hasn't specified, ask: "What do you want to learn about your users? What decisions will this data inform?"
Step 2: Analytics Platform Selection
Choose the right analytics stack:
PLATFORM SELECTION:
| Platform | Best For | Privacy Model |
|--|--|--|
| Segment | Data routing hub, | Third-party, consent needed |
| | multi-destination CDP | GDPR tools available |
| Amplitude | Product analytics, | Third-party, consent needed |
| | behavioral cohorts, | SOC 2, GDPR compliant |
| | journey mapping | |
| Mixpanel | Event analytics, | Third-party, consent needed |
| | funnel analysis, | EU data residency available |
| | retention tracking | |
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 · 306 lines · 31 tokens per session scan A 15039e6ef57d
analytics is a skill published in the GitHub repository arbazkhan971/godmode (26 stars, last pushed 6d ago), licensed MIT. It adds 31 tokens to every session and 2,745 once invoked, about $0.0002 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
jobs-to-be-done
Discover what customers truly need by analyzing the "job" they hire your product to do. Use when the user mentions "customer discovery", "why customers churn", "what job does this solve", "competing against luck", "product-market fit", "switching behavior", "milkshake moment", or "functional vs emotional jobs". Also…
asc-subscription-localization
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.
scienceworld-growth-focuser
Use when you have planted a seed or need to track a plant's growth stage (sprouting, flowering, reproduction). Applies the 'focus on' action to a specific plant or biological entity to signal intent and monitor its development. Trigger after planting or when you need to observe life cycle progression in the…
ralph-specum-requirements
This skill should be used only when the user explicitly asks to use $ralph-specum-requirements, or explicitly asks Ralph Specum in Codex to run the requirements phase.
biome
Repository guidance for using Biome as the formatter, linter, and code quality tool within the hr-skills monorepo.
dashboard-builder
Build and manage recurring dashboard views of key metrics — set up daily/weekly monitoring with saved metrics and segments. Use when the user wants to create a recurring dashboard, set up KPI monitoring, or establish a baseline.