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/pricing)<a href="https://agentmods.dev/commands/phuryn/pm-skills/pricing"><img src="https://agentmods.dev/badge/commands/phuryn/pm-skills/pricing/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/pricing"><img src="https://agentmods.dev/badge/commands/phuryn/pm-skills/pricing.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.00018 | $0.01002 |
| Opus 5 | $0.00009 | $0.00501 |
| Sonnet 5 | $0.00004 | $0.00200 |
| Haiku 4.5 | $0.00002 | $0.00100 |
Grade A, and why
pricing 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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pricing -- Pricing Strategy Design
Build a pricing strategy from first principles: analyze pricing models, estimate willingness to pay, benchmark against competitors, and design pricing experiments.
Invocation
/pricing SaaS project management tool moving from free to paid
/pricing Should we switch from per-seat to usage-based pricing?
/pricing [upload competitor pricing pages or current pricing data]
Workflow
Step 1: Understand the Pricing Context
Ask:
- What is the product? What value does it deliver?
- Current pricing (if any): model, price points, packaging
- What's the trigger? (new product, pricing change, competitive pressure, growth stall)
- Target customer profile and their budget context
- Any constraints? (contractual obligations, market expectations, competitive positioning)
Step 2: Analyze Pricing Models
Apply the pricing-strategy and monetization-strategy skills:
Evaluate applicable models:
- Flat-rate: Simple, predictable — best for commoditized products
- Per-seat/user: Scales with adoption — best for collaboration tools
- Usage-based: Aligns cost with value — best for infrastructure and API products
- Tiered: Captures different willingness to pay — best for segmented markets
- Freemium: Drives adoption — best for products with network effects
- Hybrid: Combines models — best for complex products with multiple value levers
For each relevant model: pros, cons, fit for your product, revenue projection approach.
Step 3: Competitive Pricing Analysis
Using web research:
- Benchmark pricing against 3-5 competitors
- Identify pricing model patterns in the category
- Note pricing trends (e.g., shift from per-seat to usage-based in B2B SaaS)
- Find pricing page screenshots and data points
Step 4: Willingness to Pay Estimation
If the user has survey data or customer feedback:
- Apply Van Westendorp analysis (if data available)
- Segment willingness to pay by user type
If no data:
- Estimate based on value delivered, competitive anchoring, and market norms
- Design a willingness-to-pay survey the user can run
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 · 129 lines · 18 tokens per session scan A 84b744adc2ee
pricing is a command published in the GitHub repository phuryn/pm-skills (26,507 stars, last pushed 7d ago), licensed MIT. It adds 18 tokens to every session and 1,002 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
retro
Facilitate a post-launch or sprint retrospective anchored to OKRs.
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.
plan-sprint
Plan the upcoming sprint — epic breakdown, user story decomposition, RICE prioritization, dependency check, and capacity allocation.
roadmap
Build or review your roadmap — OKR alignment, Now/Next/Later structuring, dependency mapping, and stakeholder views, pulling live Linear/Jira state.
set-okrs
Structure OKRs — define objectives, write measurable key results, align to strategy, stress-test for quality, and cascade across teams.
stakeholder-update
Generate tailored stakeholder updates by audience — pulls live tracker state from Linear/Jira, formats by audience (exec / engineering / customer) using Pyramid Principle.