phuryn/pm-skills is a marketplace of reusable skills, commands, and plugins that guide AI assistants through product-management work such as discovery, strategy, planning, metrics, launches, and growth. It is for product managers and teams using Claude Code, Cowork, or compatible assistants. The catalogue entries are the project's own workflows and extensions.
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/phuryn/pm-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/phuryn/pm-skills/derive-tests)<a href="https://agentmods.dev/commands/phuryn/pm-skills/derive-tests"><img src="https://agentmods.dev/badge/commands/phuryn/pm-skills/derive-tests/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/phuryn/pm-skills/derive-tests"><img src="https://agentmods.dev/badge/commands/phuryn/pm-skills/derive-tests.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.00092 | $0.02453 |
| Opus 5.5 | $0.00037 | $0.00981 |
| Sonnet 5.5 | $0.00018 | $0.00491 |
| Haiku 4.5 | $0.00009 | $0.00245 |
Grade A, and why
derive-tests 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 10d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/derive-tests -- Turn Intent Into Tests
The docs say what the system should do. An audit finds where the code doesn't. Tests are what stop that gap from reopening after the next AI edit. This command reads the documented intent, turns each load-bearing rule into a concrete test case, sorts them into what to automate, what needs a guarded live run, and what stays manual — then recommends the gate that keeps main honest: the one the repo's own instructions define, or a green-before-merge CI gate where they define none.
This produces a coverage map (tests.md) and concrete test cases, not a finished suite — you or the next agent implement the deterministic ones. If the repo already keeps a test-coverage file, under any name, that file is the map: update it rather than starting a second one (the shipping-artifacts skill's Locations and names rule).
Invocation
/derive-tests
/derive-tests the checkout flow
/derive-tests supabase/functions
/derive-tests check
/derive-tests check the checkout flow
A first argument of check runs check-only mode (below) on the scope that follows it, instead of the workflow.
Prerequisite: documented intent
Tests are derived from the docs, so the docs come first. If the system docs (in the repo's docs location, or documentation/ by default) are missing or thin, run /document-app (and /derive-tests reads flows.md, permissions.md, and automation.md most heavily). You cannot map coverage to rules you never wrote down — where intent is absent, say so rather than inventing rules to test.
The workflow
1. Read the intent — and the tests that already exist
Read the applicable system docs (architecture, flows, permissions, variables, and any of emails, cron, seo, automation that exist). Apply the shipping-artifacts skill for what each doc should contain, and the intended-vs-implemented skill for the discipline of treating docs as claims to verify, not proof.
Then inventory the existing test suite — the test files, what they actually assert, and what runs in CI today. The map you produce must distinguish coverage that exists now from coverage you're proposing; skipping this step yields a falsely-green map that claims rules are pinned when nothing checks them. If there are no tests, say so plainly — that is itself a finding.
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.
- 10d ago Changed · +38 lines · +37 tokens per session f3c7f591f017
- 1mo ago First seen · 115 lines · 55 tokens per session scan A d6727d5569b1
derive-tests is a command published in the GitHub repository phuryn/pm-skills (27,241 stars, last pushed 5d ago), licensed MIT. It adds 92 tokens to every session and 2,453 once invoked, about $0.0004 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-08-30.
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.