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/value-proposition)<a href="https://agentmods.dev/commands/phuryn/pm-skills/value-proposition"><img src="https://agentmods.dev/badge/commands/phuryn/pm-skills/value-proposition/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/value-proposition"><img src="https://agentmods.dev/badge/commands/phuryn/pm-skills/value-proposition.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.00026 | $0.00615 |
| Opus 5 | $0.00013 | $0.00308 |
| Sonnet 5 | $0.00005 | $0.00123 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
value-proposition 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/value-proposition -- Value Proposition Design
Design a clear, compelling value proposition for a product or feature using the 6-part JTBD template. An alternative to Strategyzer's Value Proposition Canvas that starts with the customer and focuses on practical outcomes.
Invocation
/value-proposition AI writing tool for non-native English speakers
/value-proposition [upload pitch deck, PRD, or competitive analysis]
/value-proposition # asks about your product
Workflow
Step 1: Understand the Product and Market
Accept context from:
- Product description (verbal or written)
- Uploaded documents (pitch decks, PRDs, competitive analyses)
- Existing value propositions to refine
Ask key questions:
- What does the product do? Who is it for?
- What alternatives or workarounds exist today?
- What customer insights or research do you have?
Step 2: Build the Value Proposition
Apply the value-proposition skill to produce the 6-part template:
## Value Proposition: [Product]
### For [Segment]:
1. **Who**: [target user profile and characteristics]
2. **Why**: [the job they're trying to do, desired outcomes]
3. **What Before**: [their current painful reality — existing tools, friction, workarounds]
4. **How**: [your solution — specific features and capabilities that deliver value]
5. **What After**: [the improved outcome — what becomes possible]
6. **Alternatives**: [what they'd use without you, and why you're better]
### Value Proposition Statement
[One sentence: For [who] who [need], [product] is a [category] that [benefit]. Unlike [alternative], we [differentiator].]
### Value Proposition Statements (Reusable)
- Marketing: [...]
- Sales: [...]
- Onboarding: [...]
If the user has multiple segments, create a separate value proposition for each.
Step 3: Save and Offer Next Steps
Save as markdown. Offer:
- "Want me to compare this against competitors with a Value Curve?"
- "Should I build a full strategy around this value proposition?"
- "Want me to create a Lean Canvas or Startup Canvas using this?"
- "Should I generate marketing messaging from these value prop statements?"
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 · 73 lines · 26 tokens per session scan A 1cc49a83cbc6
value-proposition is a command published in the GitHub repository phuryn/pm-skills (26,507 stars, last pushed 7d ago), licensed MIT. It adds 26 tokens to every session and 615 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
experiment-ideas
Generate several concrete, brain-grounded growth ideas — channel, message, rationale, cost-efficiency — ranked by effort vs. impact.
value-prop-statements
Fan an existing positioning statement out into segment- and channel-specific value-prop copy variants, trace-checked against drift.
pmm-metrics
Define a North Star Metric and capped scorecard, or audit an existing metrics list for sprawl and vanity metrics.
alternatives-map
Build or deepen your competitive alternatives map — direct competitors, adjacent tools, DIY, and status quo — from real win/loss data.
gtm-motions
Score and select a GTM motion stack against real deal economics, not a taxonomy tour.
buyer-personas
Map the buying committee, then build alternatives-anchored messaging personas.