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.
git clone --depth 1 https://github.com/stefanoskarakasis/Product-Marketing-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/commands/stefanoskarakasis/product-marketing-skills/pmm-metrics)<a href="https://agentmods.dev/commands/stefanoskarakasis/product-marketing-skills/pmm-metrics"><img src="https://agentmods.dev/badge/commands/stefanoskarakasis/product-marketing-skills/pmm-metrics/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/commands/stefanoskarakasis/product-marketing-skills/pmm-metrics"><img src="https://agentmods.dev/badge/commands/stefanoskarakasis/product-marketing-skills/pmm-metrics.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.00022 | $0.00398 |
| Opus 5 | $0.00011 | $0.00199 |
| Sonnet 5 | $0.00004 | $0.00080 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
pmm-metrics 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 7d 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.
What it actually says
/pmm-growth:pmm-metrics -- PMM Metrics
Classify the business game, define a North Star Metric validated against 7 criteria, name 3-5 Input Metrics with a stated causal link and owner, then build a capped scorecard (8-16 metrics) across Financial, Customer, Product & GTM, and Process & Growth. Rejects revenue-shaped North Star candidates and flags vanity metrics nobody can move.
Invocation
/pmm-growth:pmm-metrics Help me define our North Star metric
/pmm-growth:pmm-metrics Build a scorecard for leadership reporting
/pmm-growth:pmm-metrics Our metrics list has 25 things and nobody updates it
Workflow
Uses the pmm-metrics skill. Loads brain Sections 1/2 if present,
classifies the business game (Attention/Transaction/Productivity),
proposes and validates a North Star Metric against all 7 criteria
(rejecting revenue-shaped candidates by name), defines 3-5 Input Metrics
each with a causal link and named owner, builds a capped scorecard with
targets/weights/cadence, runs a sprawl and vanity-metric self-check, then
delivers the result in chat — this skill writes no output file, and
closes with a session log to /context/skill-sessions.md.
Commands
/classify— business game classification only/north-star— business game + NSM + Input Metrics, skip the scorecard/scorecard— scorecard only, assuming NSM/Input Metrics are already set/audit— pressure-test an existing metrics list for sprawl and vanity metrics
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.
- 7d ago First seen · 39 lines · 22 tokens per session scan A a39c38c50166
pmm-metrics is a command published in the GitHub repository stefanoskarakasis/Product-Marketing-Skills (5 stars, last pushed 6d ago), licensed MIT. It adds 22 tokens to every session and 398 once invoked, about $0.0001 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-09-15.
Other commands, from other repositories
brief-me
Get briefed — loads your full memory, pulls live state from all connected tools, surfaces risks, staleness, upcoming milestones, and gives you a prioritized briefing so you're never starting blank.
design-ai-feature
Design an AI-powered feature end-to-end — model selection, prompt architecture, eval framework, failure modes, cost modeling, and improvement flywheel.
discover
Run a full discovery cycle — problem framing, JTBD demand-side analysis, assumption mapping, opportunity sizing, and OST mapping — from a rough idea to validated opportunity.
competitive-intel
Run a competitive intelligence analysis — landscape mapping, battlecards, 7 Powers moat comparison, positioning gaps, and monitoring plan.
plan-launch
Plan a full go-to-market launch — positioning, messaging hierarchy, ICP definition, launch timeline, rollback plan, and post-launch measurement.
plan-sprint
Plan the upcoming sprint — epic breakdown, user story decomposition, RICE prioritization, dependency check, and capacity allocation.