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.
npx skills add phuryn/pm-skills --skill test-scenariosgit 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/skills/phuryn/pm-skills/test-scenarios)<a href="https://agentmods.dev/skills/phuryn/pm-skills/test-scenarios"><img src="https://agentmods.dev/badge/skills/phuryn/pm-skills/test-scenarios/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/phuryn/pm-skills/test-scenarios"><img src="https://agentmods.dev/badge/skills/phuryn/pm-skills/test-scenarios.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00052 | $0.00715 |
| Opus 5 | $0.00026 | $0.00358 |
| Sonnet 5 | $0.00010 | $0.00143 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
test-scenarios 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- test-scenarios — 100% identical, 0 lines differ
- test-scenarios — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Scenarios
Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step test actions, and expected outcomes.
Use when: Writing QA test cases, creating test plans, defining acceptance test scenarios, or validating user story implementations.
Arguments:
$PRODUCT: The product or system name$USER_STORY: The user story to test (title and acceptance criteria)$CONTEXT: Additional testing context or constraints
Step-by-Step Process
- Review the user story and acceptance criteria
- Define test objectives - What specific behavior to validate
- Establish starting conditions - System state, data setup, configurations
- Identify user roles - Who performs the test actions
- Create test steps - Break down interactions step-by-step
- Define expected outcomes - Observable results after each step
- Consider edge cases - Invalid inputs, boundary conditions
- Output detailed test scenarios - Ready for QA execution
Scenario Template
Test Scenario: [Clear scenario name]
Test Objective: [What this test validates]
Starting Conditions:
- [System state required]
- [Data or configuration needed]
- [User setup or permissions]
User Role: [Who performs the test]
Test Steps:
- [First action and its expected result]
- [Second action and observable outcome]
- [Third action and system behavior]
- [Completion action and final state]
Expected Outcomes:
- [Observable result 1]
- [Observable result 2]
- [Observable result 3]
Example Test Scenario
Test Scenario: View Recently Viewed Products on Product Page
Test Objective: Verify that the 'Recently viewed' section displays correctly and excludes the current product.
Starting Conditions:
- User is logged in or has browser history enabled
- User has viewed at least 2 products in the current session
- User is now on a product page different from previously viewed items
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 · 87 lines · 52 tokens per session scan A 2dc10ebb6359
test-scenarios is a skill published in the GitHub repository phuryn/pm-skills (26,161 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 715 once invoked, about $0.0003 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
meta-verify
Runs a second-pass quality check on a skill's output before it goes out — re-checks it against the originating skill's own Quality Gate and Operating Rules, and returns specific fixes rather than a pass/fail verdict alone. Trigger on: "verify this", "check this before I send it", "second-pass this brief", "did that…
eval-suite-design
Use this skill when the user asks to "design an eval suite", "build evals for my AI feature", "create an evaluation framework", "how do I evaluate my AI", "what evals should I run", "build an eval system", or wants to create a systematic evaluation framework for an AI-powered product feature. Typically run after…
regression-testing
Use this skill when the user asks to "prevent regressions in AI quality", "regression testing for AI", "how do I know if a prompt change broke something", "before/after evaluation for model changes", "catch quality regressions", or wants to set up a process that catches when a model update, prompt change, or system…
pmm-resume
Resume reviewer and tailoring engine for Product Marketing Managers (IC to VP, including AI PMM roles). Takes baseline resume + job description → dissects JD → ranks bullets by impact fit → rebuilds complete resume in one pass. Trigger on: resume + JD paste, "tailor this", "which bullets for this role", "rebuild for…
prd
Guides Product Managers and Product Marketing Managers to co-create complete Product Requirements Documents with embedded Solution Stories. Reads brain context (positioning, ICP, Revenue Levers) to anchor PRDs in strategy. Outputs: structured Solution Story for GTM communications + full PRD for execution alignment.
pre-mortem
Identifies and pressure-tests failure modes for any strategic initiative (product launch, pricing change, GTM pivot, new market entry, feature rollout) by running a cross-functional risk exercise. Loads brain context (ICP, positioning, competitive landscape) and, when available, guardrails from prior pre-mortems…