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-onboardinggit 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-onboarding)<a href="https://agentmods.dev/skills/shiroryu9/community-ops-kit/community-ops-onboarding"><img src="https://agentmods.dev/badge/skills/shiroryu9/community-ops-kit/community-ops-onboarding/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-onboarding"><img src="https://agentmods.dev/badge/skills/shiroryu9/community-ops-kit/community-ops-onboarding.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.00063 | $0.00572 |
| Opus 5 | $0.00032 | $0.00286 |
| Sonnet 5 | $0.00013 | $0.00114 |
| Haiku 4.5 | $0.00006 | $0.00057 |
Grade A, and why
community-ops-onboarding 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Community Ops Onboarding
Use this skill when the problem is entry, activation, first action, role/access routing, or early retention.
Project Inputs
Get the relevant community-specific context from the user or an approved source: target newcomer segment, entry source, current welcome/rules/start surfaces, intended first action, roles and access rules, known friction and evidence, and support or safety boundaries. Unknown fields may remain data gaps during diagnosis.
The skill supplies the path-design method. It does not supply channel names, role names, permission rules, age/content policies, product steps, or activation data. Do not inherit those values from examples or another community. Ask only for missing context that changes the diagnosis, access safety, or proposed first action.
First Move
Map the newcomer path:
discovery -> entry -> identity/intent -> first action -> feedback/help -> second action
Do not start by rewriting welcome copy. First find where the path breaks.
Surface Jobs
Assign one job to each surface:
- invite / landing page: set expectation;
- onboarding questions: segment and route safely;
- rules: define boundaries;
- welcome / start-here: give one first action;
- guide / pinned post: explain details;
- first activity or checklist: create participation;
- support path: handle confusion or access problems.
Avoid making every surface repeat every CTA.
Output Pattern
**Diagnosis**
[Where newcomers currently get stuck.]
**Newcomer Segments**
| Segment | Need | First action | Risk |
|---|---|---|---|
**Path**
1. Entry: ...
2. Intent/role routing: ...
3. First action: ...
4. Feedback/help: ...
5. Second action: ...
**Surface Changes**
| Surface | Current issue | Change | Owner gate |
|---|---|---|---|
**Activation Evidence**
- onboarding completion;
- first post/comment/submission;
- first product/account action;
- support questions reduced;
- day 1 / day 7 return signal if available.
Guardrails
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.
- 10d ago First seen · 74 lines · 63 tokens per session scan A 99a9c9bd8069
community-ops-onboarding is a skill published in the GitHub repository ShiroRyu9/community-ops-kit (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 63 tokens to every session and 572 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
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.