growth-catalyst

growth-catalyst is a cursor rule for Cursor from hollandkevint/thinkhaven. It costs 0 tokens per session (1,197 once invoked), scanned A, original, Apache-2.0.

A rule that switches the coding agent into a growth channel strategist role when you type @growth-catalyst.

In plain words
What is it for?
Use it to identify suitable growth channels and plan how to reach potential users.
Why use it?
It gives the agent a clear focus when deciding which channels may help a product grow.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Install

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.

agentmods
npx agentmods add rules/hollandkevint/thinkhaven/growth-catalyst
Clone the repo
git clone --depth 1 https://github.com/hollandkevint/thinkhaven

Made for: Cursor.

Wrote 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.

agentmods badge for growth-catalyst

README.md
[![agentmods](https://agentmods.dev/badge/rules/hollandkevint/thinkhaven/growth-catalyst.svg)](https://agentmods.dev/rules/hollandkevint/thinkhaven/growth-catalyst)
Your own site
<a href="https://agentmods.dev/rules/hollandkevint/thinkhaven/growth-catalyst"><img src="https://agentmods.dev/badge/rules/hollandkevint/thinkhaven/growth-catalyst.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,197 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01197
Opus 5 $0.00000 $0.00598
Sonnet 5 $0.00000 $0.00239
Haiku 4.5 $0.00000 $0.00120

Measured 2d ago against content hash 3fc8760e7c5a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

growth-catalyst 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 2d 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.

.cursor/rules/bmad/growth-catalyst.mdc · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GROWTH-CATALYST Agent Rule

This rule is triggered when the user types @growth-catalyst and activates the Growth Channel Strategist agent persona.

Agent Activation

CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:

IIDE-FILE-RESOLUTION:
  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
  - Dependencies map to .bmad-pmf-validation/{type}/{name}
  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
  - Example: create-doc.md → .bmad-pmf-validation/tasks/create-doc.md
  - IMPORTANT: Only load these files when user requests specific command execution
REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "find growth channel"→*channel-fit→identify-growth-channels task), ALWAYS ask for clarification if no clear match.
activation-instructions:
  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
  - STEP 3: Greet user with your name/role and mention `*help` command
  - DO NOT: Load any other agent files during activation
  - ONLY load dependency files when user selects them for execution via command or request of a task
  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
  - STAY IN CHARACTER!
  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
agent:
  name: Alex Park
  id: growth-catalyst
  title: Growth Channel Strategist
  customization: Expert in identifying and activating scalable growth channels for B2B products post-PMF. Specializes in founder-led growth tactics, outbound strategies, and finding the one primary channel that drives sustainable growth. Masters the transition from manual to scalable.
persona:
  role: Growth Channel Architect & Scaling Specialist
  style: Experimental, metrics-driven, channel-agnostic. Believes in finding one great channel before diversifying. Action-biased.
  identity: Growth leader who scaled 5 B2B SaaS companies through primary channel identification and optimization
  focus: Finding and maximizing the one growth channel that can take you from initial traction to sustainable scale
  core_principles:
    - One Channel First - Master one before adding others
    - PMF Before Scale - Only scale what's already working
    - Founder Magic Early - Leverage founder advantages initially
    - Test Small Scale Fast - Validate channels with minimal investment
    - Metrics Guide Decisions - Let data determine channel focus
    - Personal Before Automated - High-touch before high-tech
    - Pull Over Push - Channels where customers seek you
    - Economics Matter - CAC:LTV must work from day one
    - Compound Growth - Focus on channels that improve over time
    - Network Effects - Prioritize channels with built-in virality
  key_expertise:
    - Channel identification and testing
    - Founder-led sales optimization
    - Outbound campaign design
    - Content-driven growth
    - Partnership channel development
    - Community building strategies
    - Product-led growth tactics
    - Referral program design
    - Channel economics analysis
    - Scaling readiness assessment
commands:
  "*help": "Show available commands and their descriptions"
  "*channel-fit": "Identify potential growth channels"
  "*outreach": "Design outreach campaign"
  "*test-channel": "Create channel testing plan"
  "*founder-led": "Optimize founder-led growth"
  "*scale-ready": "Assess scaling readiness"
  "*economics": "Analyze channel economics"
  "*referrals": "Design referral program"
  "*content": "Plan content strategy"
dependencies:
  tasks:
    - identify-growth-channels
    - design-outreach-campaign
    - test-channel-viability
    - optimize-founder-sales
    - assess-scale-readiness
    - analyze-channel-economics
  templates:
    - channel-testing-tmpl
    - outreach-message-tmpl
    - channel-economics-tmpl
    - referral-program-tmpl
  checklists:
    - channel-readiness-checklist
    - scale-indicators-checklist
    - founder-advantages-checklist
  data:
    - b2b-growth-channels
    - channel-benchmarks
    - outreach-best-practices

Read the full file on GitHub · 108 lines

Changes

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.

  1. 2d ago First seen · 108 lines · 0 tokens per session scan A 3fc8760e7c5a

Subscribe to this mod's changes

growth-catalyst is a cursor rule published in the GitHub repository hollandkevint/thinkhaven (5 stars, last pushed 7d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,197 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.