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 ericrisco/rsc-harness --skill communitygit clone --depth 1 https://github.com/ericrisco/rsc-harnessWrote 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/ericrisco/rsc-harness/community)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/community"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/community/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/ericrisco/rsc-harness/community"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/community.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00077 | $0.03349 |
| Opus 5.5 | $0.00031 | $0.01340 |
| Sonnet 5.5 | $0.00015 | $0.00670 |
| Haiku 4.5 | $0.00008 | $0.00335 |
Grade A, and why
community 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 1mo 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
community
Run the community like a product with a job, not a vanity chat room. The space — a Discord server, a Telegram group+channel, a Circle — is the product. Onboarding is activation, rituals are the feature, moderation is reliability, and one north-star metric tied to your purpose is the only number that matters. A room with 5,000 silent members is a failed product, not a big one. Design the system around the conversation, not the conversation itself.
When NOT to use — route instead
| The ask | Route to |
|---|---|
| Stop paying customers of a product/SaaS from churning (win-back, lifecycle, NPS) | retention |
| Write the one-to-many broadcast email that nurtures the list | ../newsletter/SKILL.md |
| Schedule / cross-post public posts across X, LinkedIn, Instagram | ../social-publisher/SKILL.md |
| Run a single timed live event end-to-end (registration, speakers, replay) | webinar |
| Build an automated support desk / ticket triage | customer-support |
| Actually code or host the Discord/Telegram bot (gateway, slash handlers) | whatsapp-telegram, automation-flows |
| Define the voice/name/tone the community speaks in | ../brand-voice/SKILL.md |
You own the persistent, two-way space and its ongoing operating rhythm. The boundary that bites most: retention keeps buyers of a product from churning; you keep members of a shared space active and contributing. They rhyme (cohorts, re-activation) but the subject differs — a SaaS seat vs a Discord membership.
Step 0 — Purpose & north-star gate
Do not design a single channel until you have (a) a one-line purpose and (b) one business metric tied to it. Why: a community without a job becomes a dead chat — there is no signal to design toward, so you sprawl channels and beg for activity. This is the most common cause of graveyards.
If either is missing, STOP and ask one focused batch, then proceed:
- In one sentence, what is this community for — and for whom?
- What single business outcome does it move? (support deflection, retention uplift, expansion revenue, qualified referrals — pick ONE)
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 199 lines · 77 tokens per session scan A f05ef2be53e0
community is a skill published in the GitHub repository ericrisco/rsc-harness (232 stars, last pushed yesterday), licensed MIT. It adds 77 tokens to every session and 3,349 once invoked, about $0.0003 per session on Opus 5.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
batch
Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use /batch followed by operation and file pattern. For many independent single-turn transforms (translate/rewrite/extract each file into a new file) that can wait…
batch-api
Prepare a many-file, single-turn transform (translate, rewrite, extract) as a plan and submit it to the asynchronous, half-price DashScope Batch API; results are delivered as new files hours later. Invoke explicitly with /batch-api.
loop
Create a loop that runs a prompt now and follows up either on a fixed schedule or through self-paced wakeups. Usage - /loop check the build, /loop 5m check the build, /loop check the PR every 30m. /loop list to show jobs, /loop clear to cancel all.
openrig-herdr
Use when opening OpenRig fleet terminals as a herdr wall — turning a rig, pod, mission, slice, or saved view into live interactive agent tiles via rig terminal, watching another rig read-only, or driving herdr on an agent's request ("open all my rigs + a mission as views"). Covers the rig terminal open|views|status…
mission-slice-sop
Use when starting, building, handing off, restoring, or closing a mission or slice under the default lightweight SDLC.
todos
Use when the user asks for a shared plan, a task needs at least three substantive execution steps, or a loose TODO is pending. Without an explicit plan request, not for one-shot answers or checks, or one- to two-step work that is not already in the list.