agentmods.dev

froggo-mission-control: Skill for Claude Code

.claude/skills/triage-protocol/SKILL.md

triage-protocol is a skill for Claude Code from ProfFroggo/froggo-mission-control. It costs 39 tokens per session (1,275 once invoked), scanned A, original, Apache-2.0.

Standard process for classifying, prioritizing, and routing incoming messages — ensuring every item lands with the right agent at the right priority level with no messages left unclassified.

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 →

not rated 2repo 6mo ago A scan 39 tokens original Apache-2.0
View source ↗ ProfFroggo/froggo-mission-control
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/triage-protocol/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 triage-protocol

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/proffroggo/froggo-mission-control/triage-protocol"><img src="https://agentmods.dev/badge/skills/proffroggo/froggo-mission-control/triage-protocol.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,275 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.00039 $0.01275
Opus 5.5 $0.00016 $0.00510
Sonnet 5.5 $0.00008 $0.00255
Haiku 4.5 $0.00004 $0.00128

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

Security

Grade A, and why

triage-protocol 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/triage-protocol/SKILL.md · 144 lines

How it starts

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

Triage Protocol

Purpose

Process the inbox with speed and precision. Every message gets a category, a priority, and a destination. Nothing sits unclassified. Inbox does not respond, decide, or act — it reads, tags, and routes.

Trigger Conditions

Load this skill when:

  • A new message arrives that needs routing
  • Processing a batch of queued inbox items
  • Reviewing the inbox for unprocessed or misrouted items
  • Building a digest of low-priority items for owner review

Procedure

Step 1 — Read the Message

Read the full message before classifying. Do not skim. Note:

  • Sender identity (known agent, external contact, system alert, unknown)
  • Channel / source (direct message, Discord, email, webhook, internal task)
  • Apparent intent (what does the sender want or report?)
  • Any urgency signals (words like "urgent", "down", "blocked", error codes, alerts)

Step 2 — Classify the Message Type

Category Description Examples
request Someone wants something done "Can you build X?", "Please analyze Y"
question Someone needs information "What is the status of Z?", "How does X work?"
update Status or progress report "Task X is done", "Deployment succeeded"
alert System or automated notification Error logs, monitoring alerts, CI failures
feedback Opinion or reaction to something "The new feature is confusing", "Great work on Y"
social Non-work, relationship message Greetings, congratulations, casual chat
spam No actionable content Unsolicited promotion, irrelevant newsletter
unknown Cannot determine intent Route to mission-control with full message

Step 3 — Assign Priority

Priority Criteria Response time target
critical System down, data loss risk, security incident, blocking production Immediate escalation
high Agent or human is blocked, deadline-sensitive request, P0 task follow-up Same session
normal Standard work request, question, or update Queue for next session
low FYI, social, routine update, non-urgent feedback Digest

Read the full file on GitHub · 144 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 · 144 lines · 39 tokens per session scan A 9a48b3488893

Subscribe to this mod's changes

triage-protocol is a skill published in the GitHub repository ProfFroggo/froggo-mission-control (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 39 tokens to every session and 1,275 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-11-07.

Related

triage-protocol compared with skills from other repositories

triage-protocol next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
triage-protocolProfFroggo/froggo-mission-controlSkill26mo agoApache-2.0A39Claude 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