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 varunk130/ai-gtm-skill-library --skill community-catalystgit clone --depth 1 https://github.com/varunk130/ai-gtm-skill-libraryWrote 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/varunk130/ai-gtm-skill-library/community-catalyst)<a href="https://agentmods.dev/skills/varunk130/ai-gtm-skill-library/community-catalyst"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/community-catalyst/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/varunk130/ai-gtm-skill-library/community-catalyst"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/community-catalyst.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.00057 | $0.01060 |
| Opus 5 | $0.00028 | $0.00530 |
| Sonnet 5 | $0.00011 | $0.00212 |
| Haiku 4.5 | $0.00006 | $0.00106 |
Grade A, and why
community-catalyst 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Community Catalyst (LOOP Engine)
Design the mechanisms that make your product grow itself through product experience, community engagement, and viral mechanics.
When to Use
- PLG motion design
- Community program launch
- Referral program design
- Developer ecosystem strategy
- Growth loop optimization
What You'll Need
Critical inputs (ask if not provided):
- Product and its core use case
- Current growth motion (sales-led, PLG, hybrid)
- Target user persona
Nice-to-have:
- Journey Architect output (Gates 5-7 for post-sale experience)
- Current product metrics (signups, activation, retention)
Process
Step 1: PLG Readiness Assessment
Score your product on 8 dimensions (1-5 each):
| Dimension | Question | Score Guide |
|---|---|---|
| Self-serve signup | Can users start without talking to sales? | 1=must talk to sales, 5=instant signup |
| Time-to-value | Can users see value in under 5 minutes? | 1=days/weeks, 5=under 5 minutes |
| Freemium viability | Is a free tier sustainable? | 1=no, 5=natural free tier exists |
| Network effects | Does product improve with more users? | 1=no, 5=strong network effects |
| Collaboration | Does usage naturally involve inviting others? | 1=solo use, 5=inherently collaborative |
| Integration distribution | Does product plug into existing workflows? | 1=standalone, 5=deep integrations |
| Data personalization | Can the product self-optimize with usage? | 1=static, 5=gets smarter over time |
| Virality mechanics | Can users share/embed/publish from product? | 1=private only, 5=public artifacts |
PLG Readiness = sum / 40 (percentage)
- Below 50%: PLG not primary -- focus on community and assisted growth
- 50-75%: PLG-assisted (hybrid with sales)
- Above 75%: PLG-primary viable
Step 2: LOOP Design
Four interconnected growth loops:
L - Leverage Points: Where in the product do users naturally encounter reasons to share or expand? Map these to journey Gates 5-7.
O - Onboarding Friction Audit: Walk through first-time experience step by step:
- Score each step: value delivered (1-5) vs. friction imposed (1-5)
- Remove or simplify every step where friction > value
- Target: 3 clicks or fewer to first value moment
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.
- 10d ago First seen · 101 lines · 57 tokens per session scan A 4d27dca8edfd
community-catalyst is a skill published in the GitHub repository varunk130/ai-gtm-skill-library (6 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 1,060 once invoked, about $0.0003 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
session-deep-dive
Deep qualitative analysis of high-signal sessions. Spawns subagents with v2 template, synthesizes patterns, compares against known findings. Use after /session-scan.
brainstorm
Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
plugin-dev-workflow
Guide plugin development workflow — editing skills, agents, hooks, or eval framework in this repo. Use when modifying files in plugins/elixir-phoenix/, lab/eval/, or lab/autoresearch/. Ensures changes pass eval, lint, and tests before committing.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
110-java-maven-best-practices
Use when you need to review, improve, or troubleshoot a Maven pom.xml file — including dependency management with BOMs, plugin configuration, version centralization, multi-module project structure, build profiles, or any situation where you want to align your Maven setup with industry best practices. This should…