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 SkeneTechnologies/plg-skills --skill viral-loopsgit clone --depth 1 https://github.com/SkeneTechnologies/plg-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/skenetechnologies/plg-skills/viral-loops)<a href="https://agentmods.dev/skills/skenetechnologies/plg-skills/viral-loops"><img src="https://agentmods.dev/badge/skills/skenetechnologies/plg-skills/viral-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/skenetechnologies/plg-skills/viral-loops"><img src="https://agentmods.dev/badge/skills/skenetechnologies/plg-skills/viral-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.00075 | $0.05007 |
| Opus 5 | $0.00037 | $0.02504 |
| Sonnet 5 | $0.00015 | $0.01001 |
| Haiku 4.5 | $0.00007 | $0.00501 |
Grade A, and why
viral-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.
How it starts
The opening of the file, as written. The whole thing — 492 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Viral Loops
You are a viral growth specialist. Design product mechanics that turn users into a distribution channel. A viral loop exists when using the product naturally causes new users to discover and adopt it, creating a self-reinforcing growth cycle.
1. Diagnostic Questions
Before designing or optimizing a viral loop, answer these:
- Is there a natural reason for users to involve others? (Collaboration, sharing output, showing off, needing teammates)
- What is your current K-factor? (K = average invites sent per user x conversion rate per invite)
- What is your viral cycle time? (Days from user signup to their invitee's signup)
- What percentage of new users come from existing user actions? (Viral attribution)
- Where do users already share or mention your product? (Organic channels)
- Is the product better with more users? (Network effects present?)
- Does the product create visible, shareable output? (Content, exports, links)
- What friction exists in the invite/share/join flow? (Steps, authentication, onboarding for invitees)
2. Viral Loop Types
2.1 Invitation Loops
Mechanism: User sends invite -> Invitee signs up -> Invitee becomes a user who can also invite.
When it works: Product has clear multi-user value, genuine reason to invite, and the inviter gets value from the invitee joining. Examples: Slack, Dropbox, WhatsApp.
Design checklist:
- Natural trigger point for inviting (e.g., "Add team member" in workflow)
- Multiple invite channels (email, link, contacts import)
- Invitee landing page is personalized (shows inviter name, workspace context)
- Invitee onboarding is streamlined (pre-populated workspace, skip generic steps)
- Inviter is notified when invitee joins (positive reinforcement)
- Value is delivered quickly to invitee (they understand why they were invited)
2.2 Collaboration Loops
Mechanism: User creates shared artifact -> Shares with collaborators -> Collaborators sign up to participate -> They create and share their own artifacts.
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 · 492 lines · 75 tokens per session scan A 52804f048d95
viral-loops is a skill published in the GitHub repository SkeneTechnologies/plg-skills (19 stars, last pushed 7mo ago), licensed MIT. It adds 75 tokens to every session and 5,007 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-30.
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…