tracking-plan

tracking-plan is a skill for Claude Code, Codex from krillinai/growth-skills. It costs 34 tokens per session (1,769 once invoked), scanned A, original, MIT.

A planning and checking guide for product data collection. It covers which events to record, what they mean, how users are identified, and whether the data is trustworthy.

In plain words
What is it for?
Use it to design or audit tracking for metrics, funnels, experiments, customer groups, attribution, and operational decisions. It also helps check data quality, system reconciliation, monitoring, releases, and deprecation.
Why use it?
It helps prevent misleading analytics caused by missing events, inconsistent definitions, unclear data sources, or consent problems. It also gives teams a way to review changes and retire outdated events.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to design or audit tracking for metrics, funnels, experiments, customer groups, attribution, and operational decisions. It also helps check data quality, system reconciliation, monitoring, releases, and deprecation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/krillinai/growth-skills/tracking-plan
Install

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.

Any agent
npx skills add krillinai/growth-skills --skill tracking-plan
Clone the repo
git clone --depth 1 https://github.com/krillinai/growth-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for tracking-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/krillinai/growth-skills/tracking-plan/github.svg)](https://agentmods.dev/skills/krillinai/growth-skills/tracking-plan)
Your own site
<a href="https://agentmods.dev/skills/krillinai/growth-skills/tracking-plan"><img src="https://agentmods.dev/badge/skills/krillinai/growth-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.

agentmods 80×15 button for tracking-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/krillinai/growth-skills/tracking-plan"><img src="https://agentmods.dev/badge/skills/krillinai/growth-skills/tracking-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,769 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00034 $0.01769
Opus 5 $0.00017 $0.00885
Sonnet 5 $0.00007 $0.00354
Haiku 4.5 $0.00003 $0.00177

Measured 11d ago against content hash c23f1bc81ce6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

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 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.

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.

skills/growth-measurement/references/modules/tracking-plan/SKILL.md · 101 lines

How it starts

The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Tracking & Data Quality

Integrated Capabilities

This Skill consolidates adjacent workflows behind one trigger. Use the main workflow for core requests. When a request matches a module below, read that module before executing it:

Translate decisions and value states into an implementation-ready instrumentation contract. Track the smallest set of observable facts that can support the declared metric, funnel, cohort, experiment, attribution, lifecycle, or operational decision. Do not treat a tracking plan as a list of clicks or assume an SDK event is true because it fires.

Read tracking-contract.md before defining events, properties, identity, consent, or sources. Read implementation-and-qa.md before selecting collection points, versioning schemas, releasing instrumentation, reconciling systems, or deprecating events. Use playbook-sources.md to cite the pinned Growth Playbook basis.

Select One Mode

Mode Use
design Build a new tracking specification from decisions, value states, metrics, and source-of-truth requirements
audit Test existing events, properties, identity, consent, lineage, and data quality for declared decisions
migration Version, map, dual-run, reconcile, cut over, and deprecate instrumentation without silently breaking comparability

Name one primary mode. Keep desired business meaning, implemented collection, observed data, and validated truth visibly separate.

Freeze Decision And Data Boundary

Record decision, owner, consumers, product, surface, market, language, locale, business model, entity, actor, eligible population, value states, metric definitions, experiment or campaign context, collection systems, sources of truth, identity rules, consent and purpose, data classes, retention, access, required history, release window, and prohibited data.

Read the full file on GitHub · 101 lines

Files

What ships with it

3 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.

Changes

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.

  1. 11d ago First seen · 101 lines · 34 tokens per session scan A c23f1bc81ce6

Subscribe to this mod's changes

tracking-plan is a skill published in the GitHub repository krillinai/growth-skills (43 stars, last pushed 14d ago), licensed MIT. It adds 34 tokens to every session and 1,769 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens