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 LeadMagic/gtm-skills --skill tracking-plangit clone --depth 1 https://github.com/LeadMagic/gtm-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/leadmagic/gtm-skills/tracking-plan)<a href="https://agentmods.dev/skills/leadmagic/gtm-skills/tracking-plan"><img src="https://agentmods.dev/badge/skills/leadmagic/gtm-skills/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/leadmagic/gtm-skills/tracking-plan"><img src="https://agentmods.dev/badge/skills/leadmagic/gtm-skills/tracking-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00127 | $0.04722 |
| Opus 5.5 | $0.00051 | $0.01889 |
| Sonnet 5.5 | $0.00025 | $0.00944 |
| Haiku 4.5 | $0.00013 | $0.00472 |
Grade A, and why
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 23d 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 — 441 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analytics Tracking Plan
Overview
Most companies have tracking — they just don't have a plan. Events fire into the void. Pixels fire twice (or never). Marketing attributes credit to the wrong channel. Product doesn't know what marketing tracks. Nobody trusts the data. The mistake: adding tracking ad-hoc without a unified plan. This skill covers the complete analytics tracking architecture for PLG and B2B SaaS: event taxonomy, pixel strategy, attribution architecture, CDP implementation, and the analytics stack that makes it all work together.
Authoritative Foundations
- Segment — Customer Data Platform (CDP) and Tracking Plan spec
- Amplitude — Product analytics and behavioral cohorts
- PostHog — Open-source product analytics
- Mixpanel — Event-based analytics
- Google Analytics 4 (GA4) — Web analytics and conversions
- Elena Verna (Reforge/Amplitude) — PLG analytics models
- Brian Balfour (Reforge) — Growth models and tracking — Growth loops — acquisition/retention loops, not funnel-only thinking.
- OpenView — PLG benchmarks and metrics — Expansion SaaS benchmarks — PLG, sales-assist, and GTM efficiency.
- Avo — Tracking plan governance and code generation
When to Use
Trigger phrases: "tracking plan", "analytics plan", "analytics architecture", "event tracking strategy", "pixel strategy", "CDP implementation", "analytics for PLG", "SaaS analytics stack", "unified tracking plan", "marketing tracking", "product analytics implementation", "analytics audit"
The Unified Tracking Architecture
┌─────────────────────────────────┐
│ YOUR SAAS PRODUCT │
│ (Web App, API, Backend, Email) │
└──────────┬──────────────────────┘
│
┌──────────▼──────────────────────┐
│ CDP LAYER (Segment/Rudderstack) │
│ Event Collection + Routing │
└──────┬───────────┬───────────────┘
│ │
┌─────────────────▼──┐ ┌───▼──────────────────┐
│ PRODUCT ANALYTICS │ │ MARKETING ANALYTICS │
│ Amplitude/Mixpanel │ │ GA4 / Ads Pixels │
│ PostHog │ │ Attribution Tools │
└─────────────────────┘ └───────────────────────┘
│ │
┌─────────────────▼──┐ ┌───▼──────────────────┐
│ CRM + CS ANALYTICS │ │ DATA WAREHOUSE │
│ HubSpot/Salesforce │ │ Snowflake/BigQuery │
│ Intercom/Zendesk │ │ + BI (Metabase/Looker) │
└─────────────────────┘ └───────────────────────┘
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 23d ago Changed 0446906c9268
- 1mo ago Changed 1c81159876c3
- 1mo ago Changed · +3 lines 802f6a7f4273
- 1mo ago First seen · 438 lines · 127 tokens per session scan A d9f9afd8bdf3
tracking-plan is a skill published in the GitHub repository LeadMagic/gtm-skills (67 stars, last pushed 11d ago), licensed MIT. It adds 127 tokens to every session and 4,722 once invoked, about $0.0005 per session on Opus 5.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
ai-gtm-transformation-audit
Use this skill when a GTM leader (CRO, CMO, VP Sales, RevOps, CS leader, founder) wants to know where their organization really stands on its AI GTM transformation, what is holding it there, and what to do in the next 30 days to move up. It runs a short structured interview, places the org on one of four levels…
event-lead-ingestion
Use this skill when a teammate pastes a LinkedIn URL or work email for someone they just met at a booth, dinner or conference hallway and wants that lead captured the same way every time. It resolves the person and company, checks relationship history before scoring, writes the CRM record and a structured conversation…
competitor-monitoring
Use this skill when you need to know what rival companies are doing — "what are my competitors doing", "competitor update", "competitor news", "competitive landscape", "market intel", "what's new with [company]", "track [company]", "competitor briefing", "who's making moves", "we keep losing deals to [company]" — or…
event-room-intelligence
Use this skill 1 to 3 days before any face-to-face event where you hold a registration export (a talk, conference, dinner, booth) and the question is 'I have the attendee CSV, who should I talk to?'. It maps every registrant to a company, joins the list against the live CRM, LinkedIn-verifies every person's title and…
multichannel-campaign-builder
Use this skill when someone needs a complete outbound sequence written — every touch across LinkedIn and email, not a single cold email. Produces three distinct angles to choose from, then the full sequence with each message ready to send, calibrated to the campaign type and channel mix and self-checked against a…
event-account-plan
Use this skill in the weeks before a conference, trade show, or field event, when an attendee or registration list exists and the question is which companies to work, who to talk to at each one, and what to say. Trigger on "we have the attendee list for the show", "who should we target at this conference", "build the…