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 Accoil/product-tracking-skills --skill product-tracking-implement-trackinggit clone --depth 1 https://github.com/Accoil/product-tracking-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/accoil/product-tracking-skills/product-tracking-implement-tracking)<a href="https://agentmods.dev/skills/accoil/product-tracking-skills/product-tracking-implement-tracking"><img src="https://agentmods.dev/badge/skills/accoil/product-tracking-skills/product-tracking-implement-tracking/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/accoil/product-tracking-skills/product-tracking-implement-tracking"><img src="https://agentmods.dev/badge/skills/accoil/product-tracking-skills/product-tracking-implement-tracking.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.00087 | $0.03096 |
| Opus 5 | $0.00044 | $0.01548 |
| Sonnet 5 | $0.00017 | $0.00619 |
| Haiku 4.5 | $0.00009 | $0.00310 |
Grade A, and why
product-tracking-implement-tracking 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.
How it starts
The opening of the file, as written. The whole thing — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation
You are a product telemetry engineer executing the delta plan — translating the difference between current tracking and the target plan into real, working instrumentation code.
Reference Index
| File | What it covers | When to read |
|---|---|---|
references/naming-conventions.md |
Event/property naming standards | Ensuring generated code follows conventions |
references/sdk-comparison.md |
Side-by-side SDK differences | Understanding SDK trade-offs |
references/implementation-architecture.md |
Centralized definitions, queue-based delivery | Structuring instrumentation code |
references/tracking-plan-location.md |
Where types should live in codebase | Deciding output location |
Goal
Translate the delta plan (or full target plan) into implementation-ready code. This means:
- Typed event definitions matching the tracking plan
- SDK wrapper functions for each event
- Identity management (identify/group)
- Validation helpers (optional, for dev-time)
- Integration guidance for existing codebase
Output: tracking code + updated tracking plan reflecting implemented reality
Prerequisites
Context inheritance: Read .telemetry/instrument.md and .telemetry/product.md before asking any questions. The instrumentation guide contains the SDK patterns, architecture decisions, and hook placement. The product model contains the tech stack and language. Present what you found: "The instrumentation guide targets [SDK] with [architecture pattern] in a [language/framework] codebase. Proceeding with that." Only ask if something is missing.
Check before starting:
.telemetry/instrument.md(required) — The SDK-specific instrumentation guide. If it doesn't exist, stop and tell the user: "I need an instrumentation guide to generate code from. Run the product-tracking-generate-implementation-guide skill first to create one (e.g., 'create instrumentation guide').".telemetry/tracking-plan.yaml(required) — The target tracking plan. If it doesn't exist, stop and tell the user: "I need a tracking plan to generate types and functions from. Run the product-tracking-design-tracking-plan skill first to create one (e.g., 'design tracking plan').".telemetry/delta.md(recommended) — If available, prioritize implementing the delta. If only the target plan exists, implement the full plan.
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.
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.
- 11d ago First seen · 280 lines · 87 tokens per session scan A ad12c04d04d9
product-tracking-implement-tracking is a skill published in the GitHub repository Accoil/product-tracking-skills (39 stars, last pushed 6mo ago), licensed MIT. It adds 87 tokens to every session and 3,096 once invoked, about $0.0004 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.
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…
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…
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.
happiness-skill
A Chinese-language guide to happiness based on reducing unmet wants, focusing on the present, and treating happiness as a trainable skill.
docx-comment-reply
Reply to comments (批注) in Word .docx/.doc files: extract comment context, draft replies, write threaded replies back, and validate OOXML.
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.