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 agentmods add skills/dokkabei97/forged-claude-code/community-buildernpx skills add Dokkabei97/forged-claude-code --skill community-buildergit clone --depth 1 https://github.com/Dokkabei97/forged-claude-codeWrote 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/dokkabei97/forged-claude-code/community-builder)<a href="https://agentmods.dev/skills/dokkabei97/forged-claude-code/community-builder"><img src="https://agentmods.dev/badge/skills/dokkabei97/forged-claude-code/community-builder.svg" alt="Measured on agentmods" 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.00038 | $0.00967 |
| Opus 5 | $0.00019 | $0.00483 |
| Sonnet 5 | $0.00008 | $0.00193 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
community-builder 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 5d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Community Builder - Community Strategy & Setup
Overview
Builds communities that become your startup's unfair advantage. A strong community provides feedback, support, word-of-mouth, and a moat competitors can't copy.
1. When to Apply
| Trigger | Behavior |
|---|---|
| Starting a community | Full setup guide |
| "community", "discord" | Platform-specific setup |
| Community engagement dropping | Re-engagement playbook |
2. Platform Selection
| Platform | Best For | Cost | Setup |
|---|---|---|---|
| Discord | Dev tools, gaming, tech community | Free | Fast |
| Slack | B2B, professional communities | Free (limited) | Fast |
| GitHub Discussions | Open source projects | Free | Minimal |
| Circle/Bettermode | Premium communities, courses | $$ | Medium |
| Reddit (subreddit) | Public discovery, SEO | Free | Minimal |
3. Community Setup Template
Discord Server Structure
📢 announcements (read-only, updates)
👋 introductions (new members say hi)
💬 general (main chat)
❓ help-and-support (product questions)
💡 feature-requests (product ideas)
🐛 bug-reports (issue reporting)
🏗️ show-and-tell (users share what they built)
📚 resources (guides, tutorials)
🎉 wins (celebrate user achievements)
──── Team Only ────
🔒 team-internal (private team chat)
🔒 feedback-review (review user feedback)
Community Rules
## Community Guidelines
1. **Be respectful** — Treat everyone with kindness
2. **Stay on topic** — Use the right channels
3. **No spam** — Self-promotion in designated threads only
4. **Search first** — Check if your question was already answered
5. **Share knowledge** — Help others when you can
6. **Report issues** — Flag violations to moderators
4. Growth Phases
| Phase | Size | Focus | Actions |
|---|---|---|---|
| Seed | 0-100 | Quality over quantity | Personal invites, 1:1 conversations |
| Growth | 100-1K | Engagement habits | Regular content, AMAs, challenges |
| Scale | 1K-10K | Self-sustaining | Community leaders, user-generated content |
| Mature | 10K+ | Governance | Moderation team, sub-communities |
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.
- 5d ago First seen · 138 lines · 38 tokens per session scan A 95645f4515b9
community-builder is a skill published in the GitHub repository Dokkabei97/forged-claude-code (2 stars, last pushed 6mo ago), licensed MIT. It adds 38 tokens to every session and 967 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…