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/growth-strategy)<a href="https://agentmods.dev/commands/phuryn/pm-skills/growth-strategy"><img src="https://agentmods.dev/badge/commands/phuryn/pm-skills/growth-strategy/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/growth-strategy"><img src="https://agentmods.dev/badge/commands/phuryn/pm-skills/growth-strategy.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.00971 |
| Opus 5 | $0.00009 | $0.00485 |
| Sonnet 5 | $0.00004 | $0.00194 |
| Haiku 4.5 | $0.00002 | $0.00097 |
Grade A, and why
growth-strategy 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- growth-strategy — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/growth-strategy -- Growth Loops & GTM Motions
Identify and design the growth mechanisms that will drive sustainable traction. Evaluates five growth loop types and seven GTM motions to build a balanced acquisition and expansion strategy.
Invocation
/growth-strategy B2B collaboration tool — growth has stalled at 5K users
/growth-strategy Consumer fitness app looking for viral growth
/growth-strategy [upload product metrics or growth data]
Workflow
Step 1: Understand Growth Context
Ask:
- What is the product? Who uses it?
- Current growth metrics: user count, growth rate, acquisition channels
- What's working? What's not?
- Business model: how does revenue relate to user growth?
- Team and budget: what resources can you put toward growth?
Step 2: Evaluate Growth Loops
Apply the growth-loops skill:
Analyze five growth loop types for your product:
- Viral Loop: Users invite others as part of natural product use
- Usage Loop: More usage creates more value, bringing users back
- Collaboration Loop: Product becomes more valuable when used with others
- User-Generated Content Loop: Users create content that attracts new users
- Referral Loop: Satisfied users actively recommend to others
For each applicable loop: mechanism, requirements, expected impact, implementation effort.
Step 3: Evaluate GTM Motions
Apply the gtm-motions skill:
Assess seven GTM approaches:
- Inbound: Content, SEO, thought leadership
- Outbound: Sales, cold outreach, account-based
- Paid Digital: SEM, social ads, display, retargeting
- Community: Forums, events, user groups, developer relations
- Partners: Integrations, resellers, co-marketing
- ABM (Account-Based Marketing): Targeted enterprise acquisition
- PLG (Product-Led Growth): Free tier, self-serve, product virality
For each: fit for your product, expected CAC, timeline to results, tools needed.
Step 4: Design Growth Strategy
## Growth Strategy: [Product]
**Date**: [today]
**Current state**: [user count, growth rate, key channels]
**Growth goal**: [target]
### Recommended Growth Loops
| Loop Type | Mechanism | Fit | Impact | Effort | Priority |
|----------|-----------|-----|--------|--------|----------|
### Primary Growth Loop: [Type]
**How it works**: [step-by-step mechanism]
**Requirements**: [what needs to be true/built]
**Key metrics**: [how to measure loop health]
**Implementation plan**: [concrete next steps]
### Secondary Growth Loop: [Type]
[same format]
### GTM Motion Mix
| Motion | Investment | Expected ROI | Timeline | Tools |
|--------|-----------|-------------|----------|-------|
### Growth Experiments
| # | Experiment | Tests What | Effort | Expected Learning |
|---|-----------|-----------|--------|------------------|
### Growth Metrics Framework
- **North Star**: [growth metric]
- **Loop health**: [metrics per loop]
- **CAC by channel**: [tracking approach]
- **Payback period**: [target]
### 90-Day Growth Plan
**Month 1**: [focus areas and experiments]
**Month 2**: [scale what works, cut what doesn't]
**Month 3**: [optimize and systematize]
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 First seen · 117 lines · 18 tokens per session scan A 1b847aa29573
growth-strategy is a command published in the GitHub repository phuryn/pm-skills (26,131 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 971 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-08-30.
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.
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.
ideal-customer-profile
Build, enrich, or audit your ICP — trigger events, buyer map, JTBD, disqualifiers.
positioning-messaging
Build or audit positioning statements, messaging, and related output.