growth-loops

growth-loops is a skill for Claude Code, Codex from m3taz-ahmed/ai-globals. It costs 92 tokens per session (564 once invoked), scanned A, original, MIT.

A growth-marketing skill for building ways that users attract, activate, retain, and refer other users. Product-led growth means the product itself helps drive sign-ups and adoption.

In plain words
What is it for?
Use it to design referral programs, sharing mechanics, product-led growth funnels, retention campaigns, and re-engagement loops.
Why use it?
It helps replace guesswork about viral or referral campaigns with checks of real funnel data, such as activation, retention, and referrals.

Skill for Claude CodeCodex

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

Good fit Use it to design referral programs, sharing mechanics, product-led growth funnels, retention campaigns, and re-engagement loops.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/m3taz-ahmed/ai-globals/growth-loops
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 m3taz-ahmed/ai-globals --skill growth-loops
Clone the repo
git clone --depth 1 https://github.com/m3taz-ahmed/ai-globals

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/m3taz-ahmed/ai-globals/growth-loops"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/growth-loops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 92 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 564 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.00092 $0.00564
Opus 5 $0.00046 $0.00282
Sonnet 5 $0.00018 $0.00113
Haiku 4.5 $0.00009 $0.00056

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

Security

Grade A, and why

growth-loops 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.

skills/growth-loops/SKILL.md · 25 lines

What it actually says

[SKILL] growth-loops [OBJ] Engineer compounding acquisition loops — viral mechanics, referral programs, product-led growth funnels, and retention/re-activation systems. Each user should bring ≥1 new user (k-factor ≥ 1). Free-first: the viral unit must be usable without payment. RTL + Arabic parity for referral copy, share cards, and reward redemption. [RULES]

  1. [REQ] Never invent metrics — read real funnel data from analytics (PostHog/Mixpanel) before proposing loops.
  2. [REQ] Quantify the loop: k-factor, activation rate, D7/D30 retention, referral conversion rate. Present as a table.
  3. [REQ] Prefer double-sided rewards (inviter + invitee) to maximize symmetric incentive. Calculate break-even CAC vs paid acquisition.
  4. [REQ] Map the full loop: activation → retention → referral → revenue. Identify the weakest node and propose a fix.
  5. [REQ] Pick the highest-leverage loop per stage: invite (K-factor > 1), share (content virality), embed (product distribution), credit (referral economy), content (UGC flywheel).
  6. [CMD] Reuse runtime.attribution_model and runtime.funnel_tracker for measurement. Pull data via analytics_tools MCP (GA4/Mixpanel).
  7. [REQ] Document the loop as a workflow step when it spans >1 tool. Store loop metrics via aizee memory add.
  8. [REQ] Test loop viability: simulate k-factor from historical referral data before shipping. Gate behind aizee check for any automated outreach.

[PROHIBIT]

  1. No fake "limited invite" false scarcity or dark patterns.
  2. No forced-contact scraping or unauthorized address-book uploads.
  3. No paid-placement claims presented as organic virality.
  4. No bypass of approval/guardian gates for growth automations.
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 · 25 lines · 92 tokens per session scan A c930dcd5e614

Subscribe to this mod's changes

growth-loops is a skill published in the GitHub repository m3taz-ahmed/ai-globals (5 stars, last pushed yesterday), licensed MIT. It adds 92 tokens to every session and 564 once invoked, about $0.0005 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.

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

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 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