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.
npx skills add tjboudreaux/cc-plugin-product-strategist --skill product-growth-loopsgit clone --depth 1 https://github.com/tjboudreaux/cc-plugin-product-strategistWrote 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/skills/tjboudreaux/cc-plugin-product-strategist/product-growth-loops)<a href="https://agentmods.dev/skills/tjboudreaux/cc-plugin-product-strategist/product-growth-loops"><img src="https://agentmods.dev/badge/skills/tjboudreaux/cc-plugin-product-strategist/product-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.
<a href="https://agentmods.dev/skills/tjboudreaux/cc-plugin-product-strategist/product-growth-loops"><img src="https://agentmods.dev/badge/skills/tjboudreaux/cc-plugin-product-strategist/product-growth-loops.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.00023 | $0.00317 |
| Opus 5 | $0.00012 | $0.00159 |
| Sonnet 5 | $0.00005 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
product-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.
What it actually says
Growth Loop Architecture
Intent
- Replace funnel-only thinking with self-reinforcing loops that compound over time.
- Align channel, product, and community mechanics into measurable systems.
Inputs
- Current growth metrics (activation, retention, referrals, LTV/CAC).
- Channel inventory (owned, earned, paid, platform-native, on-chain incentives).
- Behavioral archetypes and motivations.
Workflow
- Loop mapping
- Enumerate existing loops (content, UGC, social proof, rewards, UGC marketplaces, token sinks/sources).
- Identify leakage points and missing steps.
- Loop design
- For each desired loop, define Trigger → Action → Reward → Investment elements and measurable KPIs.
- Ensure loops respect platform policies and economic constraints (app stores, blockchain gas, privacy laws).
- Prioritization
- Score loops on strategic fit, time-to-learn, defensibility, and required capabilities.
- Select one core loop + one accelerant loop for near-term experimentation.
- Experiment blueprint
- Specify instrumentation, success gates, and fallback plans.
- Align cross-functional owners (product, marketing, community, data).
Verification
- Every loop diagram has explicit metrics and data sources.
- Risk review covers abuse vectors, spam, and platform violations.
- Experiment backlog reflects selected loops with timelines and owners.
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 · 35 lines · 23 tokens per session scan A aed0836e8a60
product-growth-loops is a skill published in the GitHub repository tjboudreaux/cc-plugin-product-strategist (2 stars, last pushed 7mo ago), licensed MIT. It adds 23 tokens to every session and 317 once invoked, about $0.0001 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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.
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…
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…