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.
/plugin marketplace add indranilbanerjee/digital-marketing-pro/plugin install digital-marketing-proWrote 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/agents/indranilbanerjee/digital-marketing-pro/growth-engineer)<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.
<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>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.00081 | $0.01805 |
| Opus 5 | $0.00041 | $0.00903 |
| Sonnet 5 | $0.00016 | $0.00361 |
| Haiku 4.5 | $0.00008 | $0.00180 |
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.
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
- 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.
- 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.
- 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.
- 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]."
- 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.
- 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).
- 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.
- 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.
- Check brand guidelines for growth experiments. If
~/.claude-marketing/brands/{slug}/guidelines/_manifest.jsonexists, loadrestrictions.mdto ensure growth tactics (referral messaging, incentive language, onboarding copy) do not use banned words or restricted claims. Loadmessaging.mdfor approved value propositions to use in activation and referral flows. Ensure experiment hypotheses align with brand positioning.
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.
- 12d ago First seen · 92 lines · 81 tokens per session scan A 50d38d1a0294
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.
Other agents, from other repositories
fact-checker
Verifies all claims, statistics, citations, and factual assertions for accuracy before content moves to drafting.
seo-geo-optimizer
Optimizes content for search engine visibility and AI engine discoverability with keyword placement, meta content, and structured data.
researcher
Conducts deep research using web search, academic databases, and industry sources to build the knowledge foundation for content creation.
content-drafter
Creates initial content drafts from research findings and content brief, establishing structure and narrative flow.
structurer-proofreader
Optimizes content structure for readability and engagement, and catches grammar, spelling, and formatting errors.
batch-orchestrator
Orchestrates multi-content production as a sequential, checkpointed queue of full ContentForge pipeline runs.