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 matteotitta/genesys-skills --skill analytics-tracking-plangit clone --depth 1 https://github.com/matteotitta/genesys-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/matteotitta/genesys-skills/analytics-tracking-plan)<a href="https://agentmods.dev/skills/matteotitta/genesys-skills/analytics-tracking-plan"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/analytics-tracking-plan/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/matteotitta/genesys-skills/analytics-tracking-plan"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/analytics-tracking-plan.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.00137 | $0.02077 |
| Opus 5 | $0.00068 | $0.01038 |
| Sonnet 5 | $0.00027 | $0.00415 |
| Haiku 4.5 | $0.00014 | $0.00208 |
Grade A, and why
analytics-tracking-plan 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 9d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/analytics-tracking-plan — instrumentation before experiments
Build a deployable tracking plan before any experimentation or dashboarding work. Without this, every downstream measurement is phantom — /ab-testing has no events to count, /dashboard visualizes incomplete data, /signup-onboarding-audit can't measure drop-offs.
Core principle — "track for decisions, not data"
Every tracked event must inform a decision someone is making. If no one would change behavior based on a metric, don't track it. Quality > quantity: prioritize 5–10 critical events over 100 vanity metrics.
Per source data (cite-verified, MIT): consistent naming conventions prevent ~40% of implementation bugs. Conversion data needs ~48 hours to stabilize before drawing inferences.
Workflow
Step 1 — Work backward from business questions
Don't start with "what events should we track?". Start with the questions:
| Business question | Required event |
|---|---|
| "Are people signing up?" | signup_completed |
| "Are they activating?" | activation_milestone_hit (per /signup-onboarding-audit definition) |
| "Are paid users using the product?" | core_workflow_completed |
| "Are referrals converting?" | referral_clicked, referral_converted (per /referral-program) |
| "Where is acquisition coming from?" | traffic_source property on every event |
| "Does marketing $X correlate with conversion?" | UTM + signup_completed join |
If a question doesn't have a clear required event, the question isn't decision-shaped — sharpen the question first.
Step 2 — Define 5–10 critical events with Object-Action naming
Naming convention: {object}_{action} in past tense (action already happened when fired).
| Object | Action | Event name |
|---|---|---|
| signup | completed | signup_completed |
| account | created | account_created |
| trial | started | trial_started |
| trial | expired | trial_expired |
| subscription | upgraded | subscription_upgraded |
| subscription | cancelled | subscription_cancelled |
| feature_X | used | feature_X_used |
| referral | clicked | referral_clicked |
| pricing_page | viewed | pricing_page_viewed |
| demo | requested | demo_requested |
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.
- 9d ago First seen · 190 lines · 137 tokens per session scan A 4780b442bbb6
analytics-tracking-plan is a skill published in the GitHub repository matteotitta/genesys-skills (36 stars, last pushed 1mo ago), licensed MIT. It adds 137 tokens to every session and 2,077 once invoked, about $0.0007 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-09-03.
Other skills, from other repositories
gingiris-b2b-growth
🇺🇸 B2B SaaS Growth — PLG vs SLG Playbook — Diagnose whether your problem is distribution, pricing, or PMF. PLG/SLG selection by ACV and sales cycle, the 5-stage path from $0 to $10M ARR, NRR discipline, affiliate & channel motion, enterprise tiering. Built from HeyGen, Deel, Vercel, Supabase, Snowflake patterns.…
gr-b2b-growth
A guide to growing a business-to-business software product from early user research to large-scale sales. B2B software is sold to companies rather than individual consumers.
go-to-market-playbook
A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.
gingiris-go-global
🇺🇸 AI Product / SaaS Go-Global Complete SOP — From competitor research to launch to monetization. A full-cycle playbook covering Phase 0-5 (market validation, positioning, first 100 users, user interviews, beta-to-growth) plus open-source launch, Product Hunt, Reddit, SEO/GEO, conversion, and org principles.…
gr-competitor-research
Your competitor just launched. You have no idea how they grew so fast. Should you reverse-engineer their website? Track their social media? Map their growth flywheel? This gives you the complete SOP — from Wayback Machine snapshots to X/Twitter propagation analysis to growth flywheel scoring. Built from 150+ AI…
ai-launch-playbook
Launch your AI product to global attention — the playbook behind Manus, Devin, and AFFiNE's breakout launches. Covers AI-specific GTM strategy, hype cycle management, waitlist tactics, and multi-market rollout for maximum day-one impact.