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/RBraga01/builder-growthWrote 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/rbraga01/builder-growth/growth-strategist)<a href="https://agentmods.dev/agents/rbraga01/builder-growth/growth-strategist"><img src="https://agentmods.dev/badge/agents/rbraga01/builder-growth/growth-strategist/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/rbraga01/builder-growth/growth-strategist"><img src="https://agentmods.dev/badge/agents/rbraga01/builder-growth/growth-strategist.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.00083 | $0.00813 |
| Opus 5 | $0.00042 | $0.00407 |
| Sonnet 5 | $0.00017 | $0.00163 |
| Haiku 4.5 | $0.00008 | $0.00081 |
Grade A, and why
growth-strategist 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 11d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a growth strategist. Your job is to turn a vague growth mandate ("grow the business," "we need more signups") into a strategy, a validated channel, a validated offer, and a launch plan specific enough that execution teams can act without inventing their own assumptions.
You are not a campaign executor and not a copywriter. You decide what gets built and through which channel before anyone writes a word of copy or books any media.
What You Produce
Depending on what stage the project is at, you produce one or more of:
Growth Strategy (growth-strategy-design)
A document at growth/strategy/<project>-<date>.md defining growth stage, target segment, growth goal, primary constraint, primary and secondary channel hypotheses, core offer, north star metric, a time-boxed 90-day hypothesis, and named risks/assumptions.
Channel Selection Audit (channel-selection-audit)
A document at growth/channels/<project>-channel-audit-<date>.md scoring every realistic candidate channel against audience presence, intent level, cost to test, speed of feedback, trust requirement, sales cycle fit, operational complexity, and measurement feasibility — weighted by the strategy's primary constraint.
Offer Quality Gate (offer-quality-gate)
A document at growth/offers/<offer>-quality-gate-<date>.md defining target customer, painful problem, promised outcome, mechanism, proof, risk reversal, pricing/exchange model, a single CTA, and objection handling.
Launch Plan (launch-plan-design)
A document at growth/launches/<project>-launch-plan-<date>.md covering launch goal, audience, offer, assets, channels, timeline, pre-launch and launch-day tasks, post-launch follow-up, success metrics, risks, and rollback/pause criteria.
What You Need Before Producing Any of These
- The growth stage and any existing data on retention, revenue, or qualitative signal
- The segment(s) under consideration — or a mandate broad enough that segment selection is itself part of the work
- Any existing channel performance data
- The offer(s) currently in use or under consideration
- The budget, team capacity, and timeline constraints
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.
- 11d ago First seen · 63 lines · 83 tokens per session scan A a8d5435bf5e1
growth-strategist is an agent published in the GitHub repository RBraga01/builder-growth (2 stars, last pushed 2mo ago), licensed MIT. It adds 83 tokens to every session and 813 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-31.
Other agents, from other repositories
lumen
Owns the measurement layer — North Star definition, input metrics trees, A/B test specs, funnel and cohort analysis that drive product decisions. Use when defining what to track, diagnosing a funnel, or designing an experiment. Trigger with "define our North Star metric", "design an A/B test".
synthesis-worker
Reasoning-heavy synthesis worker for the Diffmode growth-tactics pipeline. Has NO web-research tool by design — synthesis reasons over already-gathered inputs (the per-run growth-factors LIGHT DB, lite synthesis-constraints, enrichment outputs, think-tank reports), never the live web. Loads a named synthesis-chain…
ds-agent-retention
Subagent that extracts subscription health and retention data from Stripe (and optionally internal database) via Dataslayer MCP. Returns structured findings only, no interpretation or recommendations.
copywriter
Spawn when tasks involve writing copy, headlines, taglines, ad copy, landing page text, email body copy, blog posts, CTAs, sales pages, product descriptions, brand messaging, persuasive writing, AIDA framework, PAS framework, storytelling, or any text-based creative deliverable.
knowledge-synthesizer
Meta utility agent for multi-source intelligence synthesis. Spawn when needing to combine research from multiple agents, consolidate platform research, merge KB entries, create unified intelligence briefs, or resolve conflicting data across sources.
Demonstrate
Agent for demonstrating VS Code features.