growth-experimenter

growth-experimenter is a skill for Claude Code, Codex from daffy0208/ai-dev-standards. It costs 49 tokens per session (4,204 once invoked), scanned A, original, MIT.

A structured way to improve user growth through experiments. It measures stages such as attracting visitors, getting sign-ups, keeping users, earning revenue, and gaining referrals.

In plain words
What is it for?
Use it to plan and evaluate experiments for acquisition, activation, retention, conversion, revenue, referrals, and other growth metrics.
Why use it?
It helps identify where people drop out of a product journey and test changes against measurable results.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to plan and evaluate experiments for acquisition, activation, retention, conversion, revenue, referrals, and other growth metrics.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/daffy0208/ai-dev-standards/growth-experimenter
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.

Any agent
npx skills add daffy0208/ai-dev-standards --skill growth-experimenter
Clone the repo
git clone --depth 1 https://github.com/daffy0208/ai-dev-standards

Made for: Claude Code, Codex.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/daffy0208/ai-dev-standards/growth-experimenter/github.svg)](https://agentmods.dev/skills/daffy0208/ai-dev-standards/growth-experimenter)
Your own site
<a href="https://agentmods.dev/skills/daffy0208/ai-dev-standards/growth-experimenter"><img src="https://agentmods.dev/badge/skills/daffy0208/ai-dev-standards/growth-experimenter/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-experimenter

Your own site · 80×15
<a href="https://agentmods.dev/skills/daffy0208/ai-dev-standards/growth-experimenter"><img src="https://agentmods.dev/badge/skills/daffy0208/ai-dev-standards/growth-experimenter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,204 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.00049 $0.04204
Opus 5 $0.00024 $0.02102
Sonnet 5 $0.00010 $0.00841
Haiku 4.5 $0.00005 $0.00420

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

Security

Grade A, and why

growth-experimenter 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 10d 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.

skills/growth-experimenter/SKILL.md · 672 lines

How it starts

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

Growth Experimenter

Run systematic experiments to grow faster through data-driven optimization.

Core Philosophy

Growth = Experimentation Velocity × Win Rate × Impact per Win

  • Run more experiments
  • Increase your hit rate through better hypotheses
  • Focus on high-impact areas

Growth Model (AARRR / Pirate Metrics)

Acquisition → Activation → Retention → Revenue → Referral
    ↓             ↓            ↓          ↓         ↓
  Traffic      Sign Up      Day 30    Upgrade   Invites
  100%          40%          50%        20%       10%

Example: 10,000 visitors/month
→ 4,000 signups (40%)
→ 2,000 active at D30 (50%)
→ 400 paying (20%)
→ 40 referrals (10%)

Improve ANY metric by 10% = 10% more customers

Where to focus first: The leakiest bucket

  • If 40% sign up but only 10% are active at D30 → Fix retention
  • If 80% are active but only 5% pay → Fix monetization
  • If 2% visitors sign up but 60% convert to paid → Get more traffic

Experiment Framework

1. Identify the Problem

Good problem statements:

  • "Only 2% of homepage visitors sign up" (specific metric)
  • "50% of trials don't complete onboarding" (clear drop-off)
  • "Users who invite teammates have 3x retention, but only 10% invite" (known behavior)

Bad problem statements:

  • "We need more growth" (too vague)
  • "Conversion is bad" (no baseline)
  • "Users don't understand the product" (not measurable)

2. Form a Hypothesis

Hypothesis template:

We believe that [change]
will result in [outcome]
because [reason/evidence]

Examples:

✅ Good:
We believe that adding social proof (testimonials) to the pricing page
will increase trial signups by 10%
because visitors currently have low trust and need validation.

✅ Good:
We believe that sending a Slack notification when user completes setup
will increase D7 activation by 20%
because users forget to come back after initial signup.

❌ Bad:
We believe that changing the button color will improve conversions
(no reason why)

❌ Bad:
We believe that improving the product will increase retention
(too vague, not testable)

Read the full file on GitHub · 672 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 10d ago First seen · 672 lines · 49 tokens per session scan A b487ffc4653a

Subscribe to this mod's changes

growth-experimenter is a skill published in the GitHub repository daffy0208/ai-dev-standards (36 stars, last pushed 8mo ago), licensed MIT. It adds 49 tokens to every session and 4,204 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens