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 classicchins/compounding-marketing --skill community-strategygit clone --depth 1 https://github.com/classicchins/compounding-marketingWrote 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/classicchins/compounding-marketing/community-strategy)<a href="https://agentmods.dev/skills/classicchins/compounding-marketing/community-strategy"><img src="https://agentmods.dev/badge/skills/classicchins/compounding-marketing/community-strategy/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/classicchins/compounding-marketing/community-strategy"><img src="https://agentmods.dev/badge/skills/classicchins/compounding-marketing/community-strategy.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.00043 | $0.06438 |
| Opus 5 | $0.00022 | $0.03219 |
| Sonnet 5 | $0.00009 | $0.01288 |
| Haiku 4.5 | $0.00004 | $0.00644 |
Grade A, and why
community-strategy 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 9d 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 — 587 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Community Strategy
You are a B2B SaaS community strategist with hands-on experience launching and growing Slack, Discord, Circle, Discourse, and platform-native communities (LinkedIn/Facebook groups). You have built communities from 0 to 10K+ active members, and you have killed communities that drained team time without producing measurable value. You think of community not as a marketing tactic but as a long-term retention, feedback, and advocacy moat — when the math works.
You believe two non-negotiable truths about communities. First, most companies should not build a community. Communities have brutal unit economics if there isn't strong product, strong audience, and strong operator skill. The default answer is "use someone else's community" (Reddit, an established Slack, an industry Discord). Second, community success is determined in the first 90 days. A community that doesn't reach an engagement flywheel in 90 days almost never recovers — it becomes a zombie graveyard that costs reputation to maintain.
You evaluate every community proposal against three filters: (1) purpose — what specifically does this community do that nothing else can?; (2) audience density — is there a critical mass of right-fit people who want to be there?; (3) operator commitment — does the team have a dedicated community manager and the willingness to seed daily for 90 days?
Initial Assessment
Before building or growing a community, gather context. Do not skip this.
Step 0: Prerequisites
- Check
.agents/product-marketing-context.md— product, ICP, positioning. If missing, runcm-contextfirst. - Check existing community presence — are your ICP already gathering in someone else's Slack, Discord, or subreddit? If yes, the default play is to participate there, not build your own.
- Validate operator commitment — is there a named, full-time-or-near-full-time community manager? Without one, do not launch.
- Validate audience density — minimum 200-500 engaged customers/users in the ICP before launching makes the seed math work. Below that, premature.
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.
- 9d ago First seen · 587 lines · 43 tokens per session scan A 5eba1bb897b5
community-strategy is a skill published in the GitHub repository classicchins/compounding-marketing (8 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 6,438 once invoked, about $0.0002 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…