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 ShiroRyu9/community-ops-kit --skill community-ops-routergit clone --depth 1 https://github.com/ShiroRyu9/community-ops-kitWrote 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/shiroryu9/community-ops-kit/community-ops-router)<a href="https://agentmods.dev/skills/shiroryu9/community-ops-kit/community-ops-router"><img src="https://agentmods.dev/badge/skills/shiroryu9/community-ops-kit/community-ops-router/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/shiroryu9/community-ops-kit/community-ops-router"><img src="https://agentmods.dev/badge/skills/shiroryu9/community-ops-kit/community-ops-router.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.00103 | $0.01518 |
| Opus 5 | $0.00051 | $0.00759 |
| Sonnet 5 | $0.00021 | $0.00304 |
| Haiku 4.5 | $0.00010 | $0.00152 |
Grade A, and why
community-ops-router 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Community Ops Router
Use this skill as the entry point for cross-functional community operations work.
Project Inputs
The kit supplies reusable judgment patterns, workflows, output structures, and safety boundaries. It does not supply a community's names, platform setup, channels, roles, activity rules, rewards, member benefits, policies, user records, credentials, or bot configuration.
Collect only the project inputs needed for the current task. Treat repository examples as demonstrations, never as defaults. If a necessary value is missing, continue with confirmed facts where useful and label the value data gap, [owner to confirm], or a question. Ask only when the missing value blocks a safe or valid result. Never request or preserve passwords, tokens, webhook URLs, full private messages, payment details, or unnecessary personal data.
Operating Model
community goal
-> user segment
-> current friction
-> next user action
-> surface
-> proof/evidence
-> feedback, support, recognition, or reward
-> review and next decision
Start with the user path and operating evidence. Do not begin with channel decoration, generic engagement tactics, or a long list of content ideas.
Read operating-principles.md when the request contains messy records, competing priorities, several possible interventions, or a need to explain why an action was chosen. Apply its evidence, minimum-change, surface-role, automation-boundary, and review rules before routing specialist work.
First Move
Classify the request:
- Diagnose: find the main break in the community lifecycle.
- Design: build an operating loop, user path, or coordinated plan.
- Route: send a concrete task to the smallest specialist skill.
- Operationalize: turn a decision into a reusable SOP with ownership, handoffs, status, verification, and writeback.
- Review: combine evidence, risks, decisions, and next actions across skills.
For multi-step work, define a lean task contract: goal, relevant context, hard constraints, required evidence, success criteria, output format, approval boundary, and stop/question conditions. See task-contract.md.
What ships with it
6 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.
- 10d ago First seen · 167 lines · 103 tokens per session scan A 1a6b1065720f
community-ops-router is a skill published in the GitHub repository ShiroRyu9/community-ops-kit (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 103 tokens to every session and 1,518 once invoked, about $0.0005 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
skool-actor
Use this skill when the user wants to read or write to a Skool community programmatically. Triggers on phrases like "list pending Skool members", "post to my Skool community", "approve all pending applicants", "publish a Skool course", "update the Auto DM message", "reply to a comment in Skool", "build a Skool course…
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
x-tweet-by-conversation
Collects every tweet in an X (Twitter) conversation thread given a conversation id (root tweet id) — the focal tweet plus all replies, sub-replies, and quote chains — and returns normalized per-tweet data with text, author, engagement counts, media, hashtags, mentions, inreplyto mapping, and cursor for pagination. Use…
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.