metrics-design

metrics-design is a skill for Claude Code from VandanaAjayDubey111/great-pm. It costs 39 tokens per session (1,081 once invoked), scanned A, original, MIT.

A product-metrics guide covering a main success measure, early and late indicators, event tracking, targets, and misleading vanity metrics.

In plain words
What is it for?
Use it to choose product metrics, define success thresholds, plan tracking events, and distinguish useful indicators from vanity metrics.
Why use it?
It helps teams measure meaningful product outcomes instead of collecting numbers that do not support decisions.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Codex.

Part of the great-pm plugin — 114 skills, 34 commands, 48 agents, 5 hooks shipped together

Good fit Use it to choose product metrics, define success thresholds, plan tracking events, and distinguish useful indicators from vanity metrics.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vandanaajaydubey111/great-pm/metrics-design
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 VandanaAjayDubey111/great-pm --skill metrics-design
Clone the repo
git clone --depth 1 https://github.com/VandanaAjayDubey111/great-pm

Made for: Claude Code.

Or install great-pm, the plugin that ships this one along with the rest of its 114 skills, 34 commands, 48 agents, 5 hooks.

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 metrics-design

README.md
[![agentmods](https://agentmods.dev/badge/skills/vandanaajaydubey111/great-pm/metrics-design/github.svg)](https://agentmods.dev/skills/vandanaajaydubey111/great-pm/metrics-design)
Your own site
<a href="https://agentmods.dev/skills/vandanaajaydubey111/great-pm/metrics-design"><img src="https://agentmods.dev/badge/skills/vandanaajaydubey111/great-pm/metrics-design/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 metrics-design

Your own site · 80×15
<a href="https://agentmods.dev/skills/vandanaajaydubey111/great-pm/metrics-design"><img src="https://agentmods.dev/badge/skills/vandanaajaydubey111/great-pm/metrics-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,081 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.00039 $0.01081
Opus 5.5 $0.00016 $0.00432
Sonnet 5.5 $0.00008 $0.00216
Haiku 4.5 $0.00004 $0.00108

Measured 1mo ago against content hash 3113b676d507, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

metrics-design 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 1mo 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/great-pm/skills/metrics-design/SKILL.md · 99 lines

How it starts

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

Codex host binding

  • Treat references to Claude slash workflows as the equivalently named Codex skill.
  • Before delegating to any specialist, read the great-pm-runtime skill and the selected packaged role file.
  • Treat "invoke", "assign", "delegate", "spawn", and source Agent-tool instructions as a required Codex spawn_agent call with that role and a bounded assignment.
  • For the spawn tool's task_name or agent_name identifier, replace canonical role-name hyphens with underscores (query-refiner-pm → query_refiner_pm). Keep canonical names unchanged in prompts, filenames, verdict logs, and user-facing output; this is an internal identifier mapping, not a role rename.
  • Store every returned agent identifier. Never call a wait tool until a spawn has returned an identifier, and wait only on identifiers returned by successful spawns.
  • If spawn_agent is unavailable or a spawn fails, report BLOCKED; do not impersonate the specialist or wait on an empty agent set.
  • Resolve bundled paths from the installed GreatPM plugin root.
  • Ignore Claude-only model aliases, colors, turn limits, and tool allowlists.
  • Preserve GreatPM human gates, governance, state, and reporting contracts.

Metrics Design — playbook

Metrics designed AFTER the build are too late. Metrics that cannot drop are vanity. The goal: ONE North Star, a few leading and lagging KPIs around it, and an instrumentation spec engineering can implement without ambiguity.

1. The North Star — one number

The North Star is the SINGLE number that, if it improves, the strategy is working.

  • Tied to a strategy bet, not to vague "engagement".
  • Measurable in a defined unit and period (e.g., "weekly active payers").
  • Honest — it has an up direction AND a credible down direction. If it cannot drop, it is vanity.

Examples by archetype:

  • B2B SaaS — weekly active accounts using a key feature.
  • Consumer app — 7-day retained users.
  • Marketplace — matched transactions per week.
  • Dev tool — weekly active projects.

Read the full file on GitHub · 99 lines

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. 1mo ago First seen · 99 lines · 39 tokens per session scan A 3113b676d507

Subscribe to this mod's changes

metrics-design is a skill published in the GitHub repository VandanaAjayDubey111/great-pm (3 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 1,081 once invoked, about $0.0002 per session on Opus 5.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-09-21.