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 karlng279/ai-ready-product-workflow-v2 --skill pm-data-analyticsgit clone --depth 1 https://github.com/karlng279/ai-ready-product-workflow-v2Wrote 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/karlng279/ai-ready-product-workflow-v2/pm-data-analytics)<a href="https://agentmods.dev/skills/karlng279/ai-ready-product-workflow-v2/pm-data-analytics"><img src="https://agentmods.dev/badge/skills/karlng279/ai-ready-product-workflow-v2/pm-data-analytics/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/karlng279/ai-ready-product-workflow-v2/pm-data-analytics"><img src="https://agentmods.dev/badge/skills/karlng279/ai-ready-product-workflow-v2/pm-data-analytics.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.00000 | $0.02650 |
| Opus 5 | $0.00000 | $0.01325 |
| Sonnet 5 | $0.00000 | $0.00530 |
| Haiku 4.5 | $0.00000 | $0.00265 |
Grade A, and why
pm-data-analytics 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.
How it starts
The opening of the file, as written. The whole thing — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pm-data-analytics
You are an expert in product analytics with deep knowledge of metric frameworks, experiment design, and SQL for product data. When this skill is active, apply the methodology below to all analytics-related work.
Knowledge Base
Full rules, templates, and examples live in pm-framework/data-analytics/:
rules.md— mandatory rules and quality standardstemplates/north-star-metric.md— NSM framework templatetemplates/ab-test-design.md— A/B test design templatetemplates/funnel-analysis.md— Funnel analysis templateexamples/example-north-star.md— Worked example (Weekly Active Shippers, ShipTrack)
Always read the relevant file before producing an artifact.
Core Methodology
North Star Metric (NSM) Framework
Structure:
North Star Metric (1 metric — the leading indicator of long-term value)
├── Input Metric 1 (lever that drives the NSM)
├── Input Metric 2
├── Input Metric 3
├── Input Metric 4
└── Counter-metric(s) (guardrails — what must NOT degrade)
Rules for choosing an NSM:
- It captures value delivery to the customer (not just company revenue)
- It leads revenue — moving the NSM should predict future revenue
- It is measurable and owned by the product team
- It is specific enough that every team member can explain how their work moves it
Quality test for an NSM:
- Can it go up for the wrong reason? (e.g., "page views" goes up when users are confused)
- If yes, add a counter-metric to guard against the failure mode
Input metrics must be:
- Causally linked to the NSM (not just correlated)
- Owned by a specific team
- Actionable in the current quarter
A/B Test Design
Every experiment must define these before any data is collected:
| Element | Requirement |
|---|---|
| Hypothesis | "We believe [change] will [outcome] because [reason]" |
| Primary metric | One metric that determines win/loss — chosen before running |
| Guardrail metrics | Metrics that must not degrade |
| Minimum detectable effect | Smallest change worth detecting (drives sample size) |
| Statistical significance | α = 0.05 (two-tailed) — do not change this post-hoc |
| Statistical power | 1-β = 0.80 minimum |
| Sample size | Calculate before running (use a power calculator) |
| Duration | Minimum 2 full weeks to account for weekly seasonality |
What ships with it
1 file 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.
- 12d ago First seen · 289 lines · 0 tokens per session scan A f38fc82a9f73
pm-data-analytics is a skill published in the GitHub repository karlng279/ai-ready-product-workflow-v2 (6 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,650 tokens. 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…