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 unixcrh/phuryn-pm-skills --skill growth-loopsgit clone --depth 1 https://github.com/unixcrh/phuryn-pm-skillsWrote 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/unixcrh/phuryn-pm-skills/growth-loops)<a href="https://agentmods.dev/skills/unixcrh/phuryn-pm-skills/growth-loops"><img src="https://agentmods.dev/badge/skills/unixcrh/phuryn-pm-skills/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/unixcrh/phuryn-pm-skills/growth-loops"><img src="https://agentmods.dev/badge/skills/unixcrh/phuryn-pm-skills/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.00054 | $0.01197 |
| Opus 5 | $0.00027 | $0.00598 |
| Sonnet 5 | $0.00011 | $0.00239 |
| Haiku 4.5 | $0.00005 | $0.00120 |
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.
This is a copy
100% identical to growth-loops — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Growth Loops
Overview
Identify and design growth loops (flywheels) that create sustainable traction. This skill evaluates five proven growth loop mechanisms to reduce reliance on paid acquisition and build product-led growth.
When to Use
- Designing growth mechanisms for a product
- Building sustainable viral or referral traction
- Reducing reliance on paid acquisition
- Analyzing competitor growth strategies
- Optimizing product for product-led growth
The 5 Growth Loop Types
1. Viral Loop
Product content created by users gets shared on external platforms, bringing new users back to the product.
- Mechanism: Users create content in-product → Share on social/external platforms → New users discover and signup
- Example: Figma designs shared as links, Loom videos shared in emails
- Strength: Exponential user acquisition if content is inherently shareable
- Challenge: Requires highly shareable output and strong incentive to share
2. Usage Loop
Users create content or value within the product, then share it, which invites new users or drives re-engagement.
- Mechanism: User creates → Shares creation → Others consume → Become engaged users
- Example: Twitter threads, Medium articles, Notion templates shared publicly
- Strength: Growth tied directly to product usage and network effects
- Challenge: Requires content creation friction to be very low
3. Collaboration Loop
Users invite colleagues to co-create or collaborate within the product, expanding the user base within organizations.
- Mechanism: User creates → Invites colleagues for collaboration → Colleagues discover product value
- Example: Google Docs invitations, Figma team projects, Slack channels
- Strength: Deep organizational penetration and high retention
- Challenge: Works best for collaborative/team-based products
4. User-Generated Loop
Users discover new content or features through other users' creations, then create and share their own content.
- Mechanism: User discovers content → Creates similar content → Shares creation → Others discover
- Example: TikTok, Pinterest, YouTube trends driving creator participation
- Strength: Creates content flywheel and network effects
- Challenge: Requires critical mass of quality content to sustain
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 · 126 lines · 54 tokens per session scan A ce93f8c3f3a5
growth-loops is a skill published in the GitHub repository unixcrh/phuryn-pm-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 54 tokens to every session and 1,197 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to growth-loops, differing in 0 lines, and is treated as a copy.
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…