rudder-instrumentation-planning

rudder-instrumentation-planning is a skill for Claude Code from rudderlabs/rudder-agent-skills. It costs 32 tokens per session (3,192 once invoked), scanned A, original, MIT.

A planning guide for deciding which events and details an application should record for analysis. An event is a tracked action, such as signing up or completing a purchase, and its properties describe that action.

In plain words
What is it for?
Use it to create a new tracking plan, choose between planning-first and code-first RudderStack workflows, or restructure existing product analytics.
Why use it?
It helps prevent missing data, excessive tracking, inconsistent event names, and dashboards that break when the tracking design changes.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the rudder-core plugin — 9 skills shipped together

Good fit Use it to create a new tracking plan, choose between planning-first and code-first RudderStack workflows, or restructure existing product analytics.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rudderlabs/rudder-agent-skills/rudder-instrumentation-planning
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 rudderlabs/rudder-agent-skills --skill rudder-instrumentation-planning
Clone the repo
git clone --depth 1 https://github.com/rudderlabs/rudder-agent-skills

Made for: Claude Code.

Or install rudder-core, the plugin that ships this one along with the rest of its 9 skills.

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 rudder-instrumentation-planning

README.md
[![agentmods](https://agentmods.dev/badge/skills/rudderlabs/rudder-agent-skills/rudder-instrumentation-planning/github.svg)](https://agentmods.dev/skills/rudderlabs/rudder-agent-skills/rudder-instrumentation-planning)
Your own site
<a href="https://agentmods.dev/skills/rudderlabs/rudder-agent-skills/rudder-instrumentation-planning"><img src="https://agentmods.dev/badge/skills/rudderlabs/rudder-agent-skills/rudder-instrumentation-planning/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 rudder-instrumentation-planning

Your own site · 80×15
<a href="https://agentmods.dev/skills/rudderlabs/rudder-agent-skills/rudder-instrumentation-planning"><img src="https://agentmods.dev/badge/skills/rudderlabs/rudder-agent-skills/rudder-instrumentation-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,192 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.00032 $0.03192
Opus 5 $0.00016 $0.01596
Sonnet 5 $0.00006 $0.00638
Haiku 4.5 $0.00003 $0.00319

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

Security

Grade A, and why

rudder-instrumentation-planning 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 12d 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.

plugins/rudder-core/skills/rudder-instrumentation-planning/SKILL.md · 487 lines

How it starts

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

Instrumentation Planning

This skill guides you through designing an instrumentation strategy - the systematic approach to deciding what events and properties to track in your application.

Why Planning Matters

Poor instrumentation leads to:

  • Data gaps - Can't answer business questions
  • Data bloat - Too many events, high costs, noise
  • Inconsistency - Same action tracked differently across teams
  • Technical debt - Constant schema changes breaking dashboards

Good instrumentation provides:

  • Complete funnel visibility - Every step from acquisition to retention
  • Consistent naming - Clear conventions everyone follows
  • Maintainable schema - Easy to extend, hard to break
  • Actionable insights - Data that drives decisions

Choose Your Workflow

Different starting points require different approaches:

Your Situation Recommended Skill
Building new feature, events not yet defined rudder-design-first-instrumentation
Existing product needs instrumentation rudder-code-first-instrumentation
Restructuring existing tracking rudder-code-first-instrumentation
General planning guidance Continue with this skill

Design-First vs Code-First

Design-First: Start from product requirements → define events → define properties → implement code. Best for new features where events are part of product definition.

Code-First: Start from existing code types → derive tracking plan → align with data governance. Best for existing products with domain types already defined.

This skill covers the general planning process. For workflow-specific guidance, see the specialized skills above.

The Planning Process

┌─────────────────────────────────────────────────────────────────────┐
│                     INSTRUMENTATION PLANNING                         │
└─────────────────────────────────────────────────────────────────────┘
         │
         ▼
┌─────────────────┐
│ 1. DISCOVERY    │ ← What questions do we need to answer?
└────────┬────────┘
         ▼
┌─────────────────┐
│ 2. TAXONOMY     │ ← What events and properties will answer them?
└────────┬────────┘
         ▼
┌─────────────────┐
│ 3. BUILD        │ ← Create the YAML definitions
└────────┬────────┘
         ▼
┌─────────────────┐
│ 4. ASSEMBLE     │ ← Group into tracking plans
└────────┬────────┘
         ▼
┌─────────────────┐
│ 5. INTEGRATE    │ ← Generate code, implement in apps
└─────────────────┘

Read the full file on GitHub · 487 lines

Files

What ships with it

2 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. 12d ago First seen · 487 lines · 32 tokens per session scan A 9a67f20e90ff

Subscribe to this mod's changes

rudder-instrumentation-planning is a skill published in the GitHub repository rudderlabs/rudder-agent-skills (18 stars, last pushed 7d ago), licensed MIT. It adds 32 tokens to every session and 3,192 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

scientific-figure-prompt-compiler

Transform concise scientific or technical descriptions into structured visual specifications and high-quality image-generation prompts. Use for scientific figures, technical diagrams, system architectures, mechanisms, workflows, spatial models, timelines, layered systems, and information-dense visuals. Model-agnostic…

basejb/skills · 72 tokens

seo-optimizer

Search Engine Optimization specialist for content strategy, technical SEO, keyword research, and ranking improvements. Use when optimizing website content, improving search rankings, conducting keyword analysis, or implementing SEO best practices. Expert in on-page SEO, meta tags, schema markup, and Core Web Vitals.

basejb/skills · 60 tokens

ai-collab-evaluator

A review of Claude Code session logs against four hiring criteria for working with AI: how you handle, use, and question AI, and how you weigh trade-offs.

basejb/skills · 169 tokens

learning-companion

A guided learning tool that turns official documents or other sources into lasting study notes through five stages, including explanation, recall, reflection, and next steps.

basejb/skills · 134 tokens

oss-tour

A guided method for learning an unfamiliar open-source repository in layers, from the whole project to folders and core modules. An open-source repository is a publicly available code project whose source can be inspected.

basejb/skills · 106 tokens

image-optimizer

An image-processing tool that converts images to WebP, an image format that can reduce file size while preserving visual quality. It handles individual images, groups of images, and whole directories.

basejb/skills · 43 tokens