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-weekly-reviewgit 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-weekly-review)<a href="https://agentmods.dev/skills/shiroryu9/community-ops-kit/community-ops-weekly-review"><img src="https://agentmods.dev/badge/skills/shiroryu9/community-ops-kit/community-ops-weekly-review/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-weekly-review"><img src="https://agentmods.dev/badge/skills/shiroryu9/community-ops-kit/community-ops-weekly-review.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.00060 | $0.00702 |
| Opus 5.5 | $0.00024 | $0.00281 |
| Sonnet 5.5 | $0.00012 | $0.00140 |
| Haiku 4.5 | $0.00006 | $0.00070 |
Grade A, and why
community-ops-weekly-review 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Community Ops Weekly Review
Use this skill to turn a week of community work into decisions and next actions.
Project Inputs
Get the review period and timezone, durable source records, action states, metric sources and denominators, user or creator signals, known risks, data gaps, and owner decisions from the user or approved project sources.
The skill supplies the review lens and output structure. It does not include the community's weekly actions, counts, revenue, retention, member records, or conclusions. If records are incomplete, review the available evidence and name the missing sources; never fill gaps with repository examples or assumed trends.
Review Lens
Review the week by operating loop, not by raw message volume:
entry -> first action -> participation -> submission/proof -> feedback/showcase -> retention/upgrade -> review
Inputs To Check
- activity launches, reminders, submissions, votes, winners, showcases;
- newcomer path and first-action signals;
- creator/high-quality content signals;
- paid member or high-value user follow-ups;
- support, payment, access, safety, or moderation risks;
- product/website/account conversion signals if available;
- unverified metrics and data gaps.
- daily operating records, execution receipts, verification results, and material state changes.
Prefer durable operating records over report summaries when the two conflict. Daily reports and dashboards are derived views; they should not become the only evidence for a weekly conclusion.
Output Pattern
Localize the visible labels to the user's requested language.
**Weekly Judgment**
[What improved, broke, or needs a decision.]
**Review Scope**
- Period/timezone: ...
- Data sources and denominator: ...
**Key Actions**
| Area | Prepared | Executed/verified | Evidence | Decision needed |
|---|---|---|---|---|
**User-Path Review**
entry -> first action -> participation -> proof -> feedback/showcase -> next action
**Opportunities**
- [Concrete improvement with surface and owner.]
**Risks / Gaps**
- [Missing data, approval, support issue, rule gap, or unclear benefit.]
**Next-Week Priorities**
1. [P0 + owner + due date]
2. [P1 + owner + due date]
3. [P2 + owner + due date]
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.
- 1mo ago First seen · 79 lines · 60 tokens per session scan A 0c555c58658e
community-ops-weekly-review is a skill published in the GitHub repository ShiroRyu9/community-ops-kit (4 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 60 tokens to every session and 702 once invoked, about $0.0002 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-31.
Other skills, from other repositories
community-ambassador-playbook
You launched an ambassador program. 3 applications. One ghosted after week 2. Should you lower the bar? Offer more perks? Spam influencers? This gives you the community & ambassador operations SOP with volunteer, paid tutorial creator and code-contributor tracks — from pre-launch checklist to recruitment to tiered…
gr-community-ambassador
You launched an ambassador program. 3 applications. One ghosted after week 2. Should you lower the bar? Offer more perks? Spam influencers? This gives you the complete community & ambassador operations SOP — from pre-launch checklist to recruitment to tiered management to retention to governance. Built from Notion…
social-media-expert
Build comprehensive social media solutions including content management, engagement tracking, influencer campaigns, and social analytics. Use when the user mentions social media content scheduling, engagement metrics, influencer campaigns, social listening, or community management.
whatsapp-community-management
Manage, automate, analyze, and operate WhatsApp groups, communities, and channels connected to the user's 9bot account. Use for scheduling messages, moderation, member management, analytics, automations, and other supported 9bot MCP operations.
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…
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…