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-paid-membersgit 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-paid-members)<a href="https://agentmods.dev/skills/shiroryu9/community-ops-kit/community-ops-paid-members"><img src="https://agentmods.dev/badge/skills/shiroryu9/community-ops-kit/community-ops-paid-members/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-paid-members"><img src="https://agentmods.dev/badge/skills/shiroryu9/community-ops-kit/community-ops-paid-members.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.00061 | $0.00524 |
| Opus 5 | $0.00030 | $0.00262 |
| Sonnet 5 | $0.00012 | $0.00105 |
| Haiku 4.5 | $0.00006 | $0.00052 |
Grade A, and why
community-ops-paid-members 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Community Ops Paid Members
Use this skill for paid members, premium users, customers, VIPs, high-value members, or users with special access/benefits.
Project Inputs
Get the segment definition, confirmed benefits, entitlement or access basis, current issue or opportunity, available evidence, support path, and approval boundary for contact, discounts, benefits, roles, or access from the user or an approved project source.
The skill supplies the operating method. It does not include customer lists, payment status, benefits, discounts, role mappings, renewal data, or outreach permission. Do not infer those values from labels such as VIP or from repository examples. Use the minimum necessary user reference and mark missing entitlement or benefit facts for owner confirmation.
Paid Member Loop
access -> value discovery -> benefit use -> support/recognition -> renewal/upgrade signal -> review
Design Questions
- What value does this segment receive beyond basic access?
- Which benefits are confirmed, and which need owner/product approval?
- What activity, support, tutorial, office hour, or showcase is exclusive to them?
- How are payment, entitlement, role, access, or discount issues escalated?
- What proves the segment is getting value?
Output Pattern
**Segment**
[Paid / premium / VIP / customer / high-value user.]
**Value Promise**
[Confirmed benefits only.]
**Operating Plan**
| Need | Action | Surface | Owner gate | Evidence |
|---|---|---|---|---|
**Care List**
- [Minimum necessary user/group reference + issue/opportunity + next follow-up.]
**Risk Boundary**
- Payment/access/discount/role changes require confirmation.
- Do not promise unconfirmed benefits.
**Review Signals**
- benefit usage;
- support resolution;
- participation;
- renewal/upgrade or churn-risk signals if available.
Guardrails
Payment, discounts, role access, paid benefits, priority support promises, and renewal claims are high-stakes. Mark them owner-confirmation needed unless explicitly confirmed. Require confirmation before outreach, mentions, public recognition, access changes, discounts, or benefit promises. Keep sensitive member issues private, use the minimum necessary user-level data, and avoid personal consumption profiles.
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 · 60 lines · 61 tokens per session scan A 2360fa625ad4
community-ops-paid-members is a skill published in the GitHub repository ShiroRyu9/community-ops-kit (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 61 tokens to every session and 524 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
implementing-llm-guardrails-for-security
Implements input and output validation guardrails for LLM-powered applications to prevent prompt injection, data leakage, toxic content generation, and hallucinated outputs. Builds a security validation pipeline using NVIDIA NeMo Guardrails Colang definitions, custom Python validators for PII detection and content…
prompting
Guide for writing effective system prompts for LLM agents. Use when creating or editing system prompts for applications, agent configurations, or development tools.
few-shot-examples
Curated few-shot examples for construction AI tasks: classification, extraction, analysis. Domain-specific examples for improved LLM performance.
prompt-templates
Reusable prompt templates for construction AI tasks: cost estimation, schedule analysis, document processing, BIM queries. Structured prompts for consistent results.
opik-optimizer
Optimize LLM prompts, tools, and agents in Opik using standardized optimizer workflows (prompt optimization, tool optimization, and parameter tuning), dataset/metric wiring, and result interpretation.
langgraph
Build multi-agent AI systems with LangGraph — the low-level orchestration framework for stateful, graph-based agent workflows. Covers supervisor, swarm, and hierarchical multi-agent patterns; subgraph composition; state management (checkpointers/stores); persistence; evals; and production debugging. Reach for this…