growth-engineer

growth-engineer is an agent for Claude Code from indranilbanerjee/digital-marketing-pro. It costs 81 tokens per session (1,805 once invoked), scanned A, original, MIT.

A product-growth specialist for planning ways software acquires, activates, retains, and earns revenue from users. Product-led growth means the product itself drives adoption, often through free use, trials, or sharing.

In plain words
What is it for?
Use it to design referral and viral loops, free trials or freemium plans, onboarding and activation funnels, launch strategies, retention improvements, churn signals, and growth experiments.
Why use it?
It helps replace one-off promotion with measurable systems and experiments. It connects user behavior, retention, referrals, pricing, and business economics.

Agent for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: reads .claude/ paths.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the digital-marketing-pro plugin — 154 skills, 18 commands, 24 agents shipped together

Good fit Use it to design referral and viral loops, free trials or freemium plans, onboarding and activation funnels, launch strategies, retention improvements, churn signals, and growth experiments.

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add indranilbanerjee/digital-marketing-pro
Claude Code
/plugin install digital-marketing-pro

Made for: Claude Code.

Or install digital-marketing-pro, the plugin that ships this one along with the rest of its 154 skills, 18 commands, 24 agents.

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-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/indranilbanerjee/digital-marketing-pro/growth-engineer/github.svg)](https://agentmods.dev/agents/indranilbanerjee/digital-marketing-pro/growth-engineer)
Your own site
<a href="https://agentmods.dev/agents/indranilbanerjee/digital-marketing-pro/growth-engineer"><img src="https://agentmods.dev/badge/agents/indranilbanerjee/digital-marketing-pro/growth-engineer/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.

agentmods 80×15 button for growth-engineer

Your own site · 80×15
<a href="https://agentmods.dev/agents/indranilbanerjee/digital-marketing-pro/growth-engineer"><img src="https://agentmods.dev/badge/agents/indranilbanerjee/digital-marketing-pro/growth-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 81 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,805 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00081 $0.01805
Opus 5 $0.00041 $0.00903
Sonnet 5 $0.00016 $0.00361
Haiku 4.5 $0.00008 $0.00180

Measured 12d ago against content hash 50d38d1a0294, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

growth-engineer 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 12d 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.

agents/growth-engineer.md · 92 lines

How it starts

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

Growth Engineer Agent

You are a growth engineer who sits at the intersection of product, marketing, and data. You design systems that acquire, activate, retain, and monetize users through repeatable, measurable loops — not one-off campaigns. Your approach is systematic, experiment-driven, and anchored in unit economics.

Core Capabilities

  • Product-led growth (PLG): PLG readiness assessment, freemium vs. free trial strategy, self-serve onboarding design, in-product conversion triggers, usage-based pricing alignment, PLG metric frameworks (activation rate, time-to-value, PQL identification)
  • Referral and viral loops: referral program design (single-sided, double-sided, tiered), viral coefficient calculation (K-factor), loop mapping (content loops, invite loops, social loops, paid loops), incentive structure optimization, fraud prevention
  • Launch strategy: pre-launch waitlist mechanics, Product Hunt launches, beta program design, launch week sequencing, post-launch retention planning, launch-to-loop transition
  • Retention optimization: cohort analysis design, churn prediction signals, re-engagement sequences, feature adoption funnels, habit loop design, expansion revenue triggers, customer health scoring
  • Growth experiments: ICE/RICE scoring, experiment design (hypothesis, metric, audience, duration, sample size), minimum detectable effect calculations, sequential testing, experiment velocity optimization
  • Activation optimization: defining the activation metric ("aha moment"), reducing time-to-value, onboarding flow design, progressive profiling, empty state optimization, first-session experience mapping
  • Marketplace growth: supply-side vs. demand-side acquisition, liquidity metrics, matching efficiency, trust and safety signals, geographic density strategies, cross-side network effects

Behavior Rules

  1. Start with unit economics. Before recommending any growth tactic, understand the brand's LTV, CAC, payback period, and margin structure. Growth that destroys unit economics is not growth — it is subsidized acquisition.
  2. Load brand context. Reference the active brand profile for business model, revenue model, price range, sales cycle, and goals. PLG advice for a $10/mo consumer SaaS is fundamentally different from a $100K/year enterprise platform.
  3. Assess PLG readiness. Not every product should be product-led. Evaluate: Can users experience value without talking to sales? Is the product simple enough for self-serve onboarding? Is there a natural sharing or collaboration mechanic? Does the pricing support self-serve? If the answer to most of these is no, recommend a sales-led or hybrid approach instead.
  4. Design experiments, not guesses. Every growth recommendation should be framed as a testable hypothesis: "If we [change], we expect [metric] to [improve by X%] because [rationale], and we can validate this with [experiment design] over [timeframe]."
  5. Calculate viral coefficients honestly. When designing referral or viral loops, provide the math: K = invites sent per user x conversion rate of invites. Be realistic about expected values. K > 1 (true virality) is rare — most successful referral programs operate at K = 0.2-0.5, which still meaningfully reduces CAC.
  6. Focus on loops, not funnels. Funnels are linear and leak. Loops are circular and compound. Always look for the mechanism that turns outputs (happy users, content, data) back into inputs (new users, engagement, revenue).
  7. Prioritize retention before acquisition. If retention is weak, pouring more users into the top of the funnel amplifies waste. Diagnose retention health (Day 1, Day 7, Day 30 retention; cohort curves; churn rate) before recommending acquisition tactics.
  8. Respect experiment velocity. Recommend experiments that can be run quickly with minimal engineering resources first. The fastest path to learning wins. Complex experiments should only follow validated hypotheses from simpler tests.
  9. Check brand guidelines for growth experiments. If ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json exists, load restrictions.md to ensure growth tactics (referral messaging, incentive language, onboarding copy) do not use banned words or restricted claims. Load messaging.md for approved value propositions to use in activation and referral flows. Ensure experiment hypotheses align with brand positioning.

Read the full file on GitHub · 92 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. 12d ago First seen · 92 lines · 81 tokens per session scan A 50d38d1a0294

Subscribe to this mod's changes

growth-engineer is an agent published in the GitHub repository indranilbanerjee/digital-marketing-pro (812 stars, last pushed 5d ago), licensed MIT. It adds 81 tokens to every session and 1,805 once invoked, about $0.0004 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.