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-support-riskgit 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-support-risk)<a href="https://agentmods.dev/skills/shiroryu9/community-ops-kit/community-ops-support-risk"><img src="https://agentmods.dev/badge/skills/shiroryu9/community-ops-kit/community-ops-support-risk/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-support-risk"><img src="https://agentmods.dev/badge/skills/shiroryu9/community-ops-kit/community-ops-support-risk.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.00067 | $0.00549 |
| Opus 5 | $0.00034 | $0.00275 |
| Sonnet 5 | $0.00013 | $0.00110 |
| Haiku 4.5 | $0.00007 | $0.00055 |
Grade A, and why
community-ops-support-risk 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 12d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Community Ops Support Risk
Use this skill when a community issue touches support, safety, payments, permissions, public claims, moderation, privacy, rewards, discounts, roles, DMs, webhooks, bots, or official account actions.
Project Inputs
Get the issue type, severity, confirmed facts, timestamps, minimum necessary user or record reference, evidence paths or IDs, applicable policy, desired resolution, and public/private boundary from the user or an approved source.
The skill supplies triage and escalation structure. It does not include a community's policy, compensation rules, account state, payment facts, moderation history, or permission data. Missing evidence remains missing. Do not import outcomes from examples, and do not request secrets, full private-message histories, payment details, or unrelated personal data.
Triage First
Classify the issue:
- access/role/permission;
- payment/discount/entitlement;
- support bug or product issue;
- moderation/safety/rules;
- reward/winner/benefit dispute;
- public copy or official claim risk;
- privacy or sensitive user data.
Risk Rule
Use the minimum access and user data needed to understand the issue. Do not execute public messaging, DMs, mentions, financial actions, rewards, discounts, role/channel/permission changes, bot/webhook changes, deletions, or official claims without explicit confirmation. When evidence is missing, ask for it or mark the item blocked.
Output Pattern
**Issue Type**
[Category and severity.]
**Confirmed Facts**
- [Who/what/where/when/evidence.]
**Missing Evidence**
- [IDs, screenshots, links, logs, policy, owner decision, etc.]
**Recommended Action**
| Priority | Action | Owner | Public/private | Risk |
|---|---|---|---|---|
**Do Not Do Yet**
- [Any send, role edit, reward, discount, DM, public claim, webhook/bot change, or deletion that needs confirmation.]
**User-Facing Draft**
[Only if requested; keep it factual and low-commitment.]
Guardrails
Do not invent policy, compensation, blame, timelines, or official product status. Do not store secrets, webhook URLs, raw private messages, personal profiles, or unnecessary sensitive data. Preserve evidence paths and timestamps when available.
What ships with it
1 file 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.
- 12d ago First seen · 58 lines · 67 tokens per session scan A 1ab2a29a62b9
community-ops-support-risk is a skill published in the GitHub repository ShiroRyu9/community-ops-kit (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 67 tokens to every session and 549 once invoked, about $0.0003 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
persona-event-coordinator
Plan and manage events — scheduling, invitations, and logistics.
persona-project-manager
Coordinate projects — track tasks, schedule meetings, and share docs.
persona-team-lead
Lead a team — run standups, coordinate tasks, and communicate.
recipe-plan-weekly-schedule
Review your Google Calendar week, identify gaps, and add events to fill them.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
recipe-review-overdue-tasks
Find Google Tasks that are past due and need attention.