Borrowing it
Nothing to install: this file belongs to hollandkevint/thinkhaven. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hollandkevint/thinkhaven/main/.claude/commands/bmadProduct/tasks/develop-growth-strategy.mdgit clone --depth 1 https://github.com/hollandkevint/thinkhavenWrote 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/hollandkevint/thinkhaven/develop-growth-strategy)<a href="https://agentmods.dev/commands/hollandkevint/thinkhaven/develop-growth-strategy"><img src="https://agentmods.dev/badge/commands/hollandkevint/thinkhaven/develop-growth-strategy.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.01938 |
| Opus 5 | $0.00000 | $0.00969 |
| Sonnet 5 | $0.00000 | $0.00388 |
| Haiku 4.5 | $0.00000 | $0.00194 |
Grade A, and why
develop-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 3d 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 — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/develop-growth-strategy Task
When this command is used, execute the following task:
Develop Growth Strategy Task
Purpose
To create a comprehensive growth strategy focusing on user acquisition, activation, retention, and monetization (AARRR) using product-led growth principles and data-driven experimentation frameworks.
Inputs
- Current product metrics and user analytics
- Customer segmentation and behavior data
- Market analysis and competitive landscape
- Business objectives and growth targets
- Product capabilities and technical constraints
- Available resources and team structure
Key Activities & Instructions
1. Establish Growth Framework
1.1 North Star Metric Definition
<critical_rule>Choose one primary metric that represents customer value creation</critical_rule>
Define your North Star:
- What action represents meaningful value for customers?
- How does this metric correlate with business success?
- Can teams directly influence this metric through product changes?
- Is it simple enough for everyone to understand?
Examples:
- "Weekly active users completing [core action]"
- "Monthly revenue from customers achieving [value milestone]"
- "Number of teams successfully [using core feature] weekly"
1.2 AARRR Funnel Analysis
Map your current funnel performance:
Acquisition: How users discover and sign up
- Traffic sources and conversion rates
- Cost per acquisition by channel
- Sign-up funnel drop-off points
- Lead quality and source attribution
Activation: First value realization
- Onboarding completion rates
- Time to first value
- Feature adoption in first session
- Setup completion rates
Retention: Continued product usage
- Day 1, 7, 30 retention rates
- Feature stickiness analysis
- Churn patterns and reasons
- Engagement scoring models
Revenue: Monetization optimization
- Conversion to paid rates
- Average revenue per user
- Pricing sensitivity analysis
- Expansion revenue opportunities
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.
- 3d ago First seen · 322 lines · 0 tokens per session scan A fdff6abc8ae8
develop-growth-strategy is a command published in the GitHub repository hollandkevint/thinkhaven (5 stars, last pushed 8d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,938 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-09-03.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.