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/ericrisco/rsc-harness/communitynpx 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.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.00077 | $0.03349 |
| Opus 5 | $0.00039 | $0.01674 |
| Sonnet 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 6d 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.
- 6d ago First seen · 199 lines · 77 tokens per session scan A f05ef2be53e0
community is a skill published in the GitHub repository ericrisco/rsc-harness (65 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 3,349 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
remindme
⏰ simple Telegram reminders for OpenClaw. cron, zero dependencies.
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
tmux-layout
Use this skill when the operator wants a prepared tmux visualization layout for the session's side-channels (STATE.md tail, CI-watch, events.jsonl tail). Renders a 4-pane default layout or debug layout. Read-only side-channel observability — the coordinator chat stays in the operator's original terminal. Trigger…
daily
Use this skill when creating today's daily note in the Meta-Vault (03-daily/YYYY-MM-DD.md) with valid vaultFrontmatterSchema-compliant YAML frontmatter. Idempotent: re-running on the same day opens the existing note instead of overwriting. Use when starting a work day, capturing scratch notes, or bootstrapping the…
agent-teams
Multi-agent team orchestration with native Agent Teams. Trigger when the user wants to launch a team of agents, coordinate parallel work with inter-agent communication, or use swarm mode.
never-stop
Use when the user explicitly requests maximum autonomous execution, no unnecessary questions, persistent recovery, independent decision-making, and continuous work until the full Definition of Done is proven.