product-tracking-instrument-new-feature

product-tracking-instrument-new-feature is a skill for Claude Code from Accoil/product-tracking-skills. It costs 122 tokens per session (2,141 once invoked), scanned A, original, MIT.

A workflow for updating an analytics tracking plan when a product feature is added, changed, or removed.

In plain words
What is it for?
Use it to update .telemetry/tracking-plan.yaml, delta.md, and changelog.md after product changes.
Why use it?
It identifies whether new events or event details are needed and keeps the plan and its change history up to date.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the product-tracking-skills plugin — 7 skills, 1 agent shipped together

Good fit Use it to update .telemetry/tracking-plan.yaml, delta.md, and changelog.md after product changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/accoil/product-tracking-skills/product-tracking-instrument-new-feature
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 Accoil/product-tracking-skills --skill product-tracking-instrument-new-feature
Clone the repo
git clone --depth 1 https://github.com/Accoil/product-tracking-skills

Made for: Claude Code.

Or install product-tracking-skills, the plugin that ships this one along with the rest of its 7 skills, 1 agent.

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 product-tracking-instrument-new-feature

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/accoil/product-tracking-skills/product-tracking-instrument-new-feature"><img src="https://agentmods.dev/badge/skills/accoil/product-tracking-skills/product-tracking-instrument-new-feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 122 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,141 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.
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.00122 $0.02141
Opus 5 $0.00061 $0.01071
Sonnet 5 $0.00024 $0.00428
Haiku 4.5 $0.00012 $0.00214

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

Security

Grade A, and why

product-tracking-instrument-new-feature 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.

skills/product-tracking-instrument-new-feature/SKILL.md · 252 lines

How it starts

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

Feature Instrumentation

You are a product telemetry engineer keeping tracking coherent as the product evolves. When a feature ships, changes, or is removed, you determine the tracking impact and apply it.

Reference Index

File What it covers When to read
references/naming-conventions.md Event/property naming standards Naming new events
references/persistence.md .telemetry/ folder structure, changelog Updating artifacts correctly
references/event-categories.md Event taxonomy and coverage Categorizing new events
references/anti-patterns.md What to avoid in tracking Reviewing new additions

Goal

When a feature ships or changes, determine:

  1. Does this need new tracking?
  2. Does it modify existing tracking?
  3. Does it need no tracking changes?

Then produce a mini delta and update the target plan.

Output: updated .telemetry/tracking-plan.yaml + .telemetry/delta.md + .telemetry/changelog.md

Prerequisites

Check before starting:

  1. .telemetry/tracking-plan.yaml (required) — The current tracking plan to update. If it doesn't exist, stop and tell the user: "I need an existing tracking plan to update. Run the product-tracking-design-tracking-plan skill first to create the initial plan (e.g., 'design tracking plan'), then come back here when a feature ships."
  2. .telemetry/product.md (recommended) — Helps calibrate tracking intensity (core vs supporting features). If missing, proceed but note the context gap.

Trigger Scenarios

Scenario Response
New feature ships Assess value, design events if needed, update plan
Existing feature changes Assess impact on existing events, modify or extend
Feature removed Deprecate related events, set removal timeline
Audit findings to fix Apply fixes from audit, update plan
Periodic review Check for stale events, coverage gaps

Batching: Multiple features can be assessed in a single session. Group changes into one version bump and one changelog entry, with sub-entries per feature. This is common at the end of a sprint when several features ship together.

Read the full file on GitHub · 252 lines

Files

What ships with it

4 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 · 252 lines · 122 tokens per session scan A 9dcb851bb13d

Subscribe to this mod's changes

product-tracking-instrument-new-feature is a skill published in the GitHub repository Accoil/product-tracking-skills (39 stars, last pushed 6mo ago), licensed MIT. It adds 122 tokens to every session and 2,141 once invoked, about $0.0006 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

high-ticket-conversion-architect

You are a Senior Conversion Architect specialized in premium B2B and luxury service sectors with offers above $10,000. Your job is not to maximize clicks, traffic, or form submissions. Your job is to engineer the page so that the right sophisticated buyer self-qualifies, builds conviction, and applies — while the…

wavect/ai-skills · 6 tokens

icp-discovery

You are a relentless ICP (Ideal Customer Profile) interrogator. Your job is to destroy vague answers and replace them with a single, specific human being in a specific situation. You use the Forces of Progress (Alan Klement), behavioral segmentation (Steve Blank), the Minimum Viable Segment (Christoph Janz), and the…

wavect/ai-skills · 4 tokens

B2B Cold Email Sequence Builder

Write high-converting B2B cold email sequences that get replies. Research-backed templates, personalization frameworks, and A/B testing plans included.

demo112/yunqu-ai-skills · 36 tokens

happiness-skill

A Chinese-language guide to happiness based on reducing unmet wants, focusing on the present, and treating happiness as a trainable skill.

kangarooking/cangjie-skill · 136 tokens

docx-comment-reply

Reply to comments (批注) in Word .docx/.doc files: extract comment context, draft replies, write threaded replies back, and validate OOXML.

foryourhealth111-pixel/Vibe-Skills · 39 tokens

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.

rorkai/app-store-connect-cli-skills · 60 tokens