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/pmprompt/claude-plugin-product-managementWrote 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/pmprompt/claude-plugin-product-management/growth)<a href="https://agentmods.dev/commands/pmprompt/claude-plugin-product-management/growth"><img src="https://agentmods.dev/badge/commands/pmprompt/claude-plugin-product-management/growth.svg" alt="Measured on agentmods" 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.00000 | $0.00302 |
| Opus 5 | $0.00000 | $0.00151 |
| Sonnet 5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
growth 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 8d 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.
What it actually says
/growth — Growth Strategy Workflow
Design self-reinforcing growth loops and retention mechanics.
What It Does
Chains growth loops, habit formation, and product-led growth to create a compounding growth engine.
When to Use
- Have initial PMF, need to scale
- Want to move beyond paid acquisition
- Design viral or retention loops
- Build habit-forming product
Workflow
-
Growth Loops — Map self-reinforcing loops where output becomes input (uses
growth-loopsskill) -
Hooked Model — Design habit loops (Trigger → Action → Reward → Investment) (uses
hooked-modelskill) -
Product-Led Growth — Structure self-serve acquisition and activation (uses
product-led-growthskill) -
Hierarchy of Engagement — Map core action → accruing benefits → mounting loss (uses
hierarchy-of-engagementskill)
Usage
/growth [product]
Example:
/growth Project management tool for agencies
Output
- 3-5 growth loop designs (viral, content, paid, sales)
- Hooked model breakdown (habit formation)
- PLG motion (acquire → activate → monetize)
- Engagement hierarchy (retention mechanics)
Next Steps After /growth
- Prioritize loops by feasibility + impact
- Build instrumentation for loop metrics
- Run experiments on top 2 loops
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.
- 8d ago First seen · 49 lines · 0 tokens per session scan A a14314e77c0c
growth is a command published in the GitHub repository pmprompt/claude-plugin-product-management (48 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 302 tokens. 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
workflow-design-sprint
Run the Design Sprint workflow (5-day prototype-and-test arc producing a Decider's build/iterate/pivot/stop call).
workflow-foundation-sprint
Run the Foundation Sprint workflow (2-day strategic-alignment arc producing a Founding Hypothesis).
chain
Run an ad-hoc ordered chain of pm-skills with shared context (ephemeral; routes to the pm-workflow-orchestrator).
workflow-foundation-to-design
Run the end-to-end Foundation Sprint + Design Sprint workflow with narrative handoff.
workflow-customer-discovery
Run the Customer Discovery workflow (research -> JTBD -> opportunities -> problem).
workflow-feature-kickoff
Run the Feature Kickoff workflow (problem -> hypothesis -> PRD -> stories).