froggo-mission-control: Skill for Claude Code

.claude/skills/community-ops/SKILL.md

community-ops is a skill for Claude Code from ProfFroggo/froggo-mission-control. It costs 26 tokens per session (1,042 once invoked), scanned A, original, Apache-2.0.

Standard operating procedures for Discord community management — channel governance, moderation workflows, engagement campaigns, and community health monitoring.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is ProfFroggo/froggo-mission-control's own configuration. It tells Claude Code how to work on froggo-mission-control itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything froggo-mission-control configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ProfFroggo/froggo-mission-control. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ProfFroggo/froggo-mission-control/dev/.claude/skills/community-ops/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/ProfFroggo/froggo-mission-control

Made for: Claude Code.

Wrote 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.

agentmods badge for community-ops

README.md
[![agentmods](https://agentmods.dev/badge/skills/proffroggo/froggo-mission-control/community-ops/github.svg)](https://agentmods.dev/skills/proffroggo/froggo-mission-control/community-ops)
Your own site
<a href="https://agentmods.dev/skills/proffroggo/froggo-mission-control/community-ops"><img src="https://agentmods.dev/badge/skills/proffroggo/froggo-mission-control/community-ops/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.

agentmods 80×15 button for community-ops

Your own site · 80×15
<a href="https://agentmods.dev/skills/proffroggo/froggo-mission-control/community-ops"><img src="https://agentmods.dev/badge/skills/proffroggo/froggo-mission-control/community-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,042 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00026 $0.01042
Opus 5.5 $0.00010 $0.00417
Sonnet 5.5 $0.00005 $0.00208
Haiku 4.5 $0.00003 $0.00104

Measured today against content hash d8d279485363, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

community-ops 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 today.

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.

.claude/skills/community-ops/SKILL.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Community Ops

Purpose

Keep the Discord community healthy, active, and well-governed. Every action taken in a community space must be intentional, documented, and approved before execution.

Trigger Conditions

Load this skill when:

  • Planning or editing channel structure or roles
  • Responding to a community issue, report, or moderation event
  • Designing or launching an engagement initiative
  • Reviewing community health metrics
  • Setting up or modifying Discord bots or automations

Procedure

Step 1 — Read Context Before Acting

Before any community action:

  1. Check memory for prior decisions about this channel/member/topic
  2. Review the relevant channel's stated purpose and community guidelines
  3. Confirm what approval level this action requires (see Approval Matrix below)

Step 2 — Classify the Situation

Situation Type Examples Initial Response
Moderation event Spam, harassment, rule violation Log → Review → Action with reason
Channel request New channel, rename, archive Draft proposal → Approval
Engagement task Event planning, contest, AMA Draft plan → Approval
Bot / automation New webhook, bot command Draft config → Test in staging → Approval
Community health Low activity, sentiment shift Analysis report → Recommendations

Step 3 — Approval Matrix

Never execute Discord actions directly without following this gate:

Action Type Approval Required
Responding to a member with advice Self (log it)
Posting a community update mission-control sign-off
Muting a member mission-control sign-off
Banning a member Human review (owner)
Creating / deleting a channel mission-control sign-off
Adding / changing bot config Human review
Launching an engagement campaign mission-control sign-off

Step 4 — Moderation Workflow

When handling a moderation situation:

  1. Document first: Who, what channel, what content, timestamp
  2. Assess severity:
    • Low: Warn message (off-topic, minor rule)
    • Medium: Mute (repeated violations, disruptive)
    • High: Escalate to ban → human review required
  3. Draft the action with reason text (visible to member and logged)
  4. Route for approval based on severity
  5. Execute after approval — never pre-emptively
  6. Log outcome in task activity with resolution

Read the full file on GitHub · 125 lines

Changes

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.

  1. today First seen · 125 lines · 26 tokens per session scan A d8d279485363

Subscribe to this mod's changes

community-ops is a skill published in the GitHub repository ProfFroggo/froggo-mission-control (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 26 tokens to every session and 1,042 once invoked, about $0.0001 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-11-07.

Related

community-ops compared with skills from other repositories

community-ops next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
community-opsProfFroggo/froggo-mission-controlSkill26mo agoApache-2.0A26Claude Code
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143ktodayMITA103Claude Code