How ProfFroggo/froggo-mission-control configures Claude Code

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/support-escalation/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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/proffroggo/froggo-mission-control/support-escalation/github.svg)](https://agentmods.dev/skills/proffroggo/froggo-mission-control/support-escalation)

Your own site

<a href="https://agentmods.dev/skills/proffroggo/froggo-mission-control/support-escalation"><img src="https://agentmods.dev/badge/skills/proffroggo/froggo-mission-control/support-escalation/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/proffroggo/froggo-mission-control/support-escalation"><img src="https://agentmods.dev/badge/skills/proffroggo/froggo-mission-control/support-escalation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,986 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.

Model	Per session	Once invoked
Fable 5.1	$0.00038	$0.02986
Opus 5.5	$0.00015	$0.01194
Sonnet 5.5	$0.00008	$0.00597
Haiku 4.5	$0.00004	$0.00299

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

Security

Grade A, and why

support-escalation 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/support-escalation/SKILL.md · 306 lines

How it starts

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

Support Escalation

Purpose

Route support issues to the right destination with the right urgency, the first time. A misrouted escalation delays resolution and frustrates users. An un-escalated issue that should have been escalated causes incidents. This process eliminates both failure modes.

Trigger Conditions

Load this skill when:

A support issue arrives that cannot be resolved immediately by the customer-success agent
An issue requires input from product, engineering, finance, or a human owner
A support issue involves potential security, data loss, or financial impact
Evaluating the urgency and routing of an open support queue
Following up on a previously escalated issue that has not been resolved within SLA

Escalation Tier Definitions

Tier 1 — CS Handles Independently

Customer-success agent resolves without escalation.

Characteristics:

Common, well-documented issue type
Resolution is within CS agent's authority
No system access, financial action, or engineering change required
No risk of data loss, security breach, or user financial harm

Examples:

Account navigation questions ("Where do I find my transaction history?")
Explaining a feature or product behavior
Resending a confirmation email
Clarifying fee structure or trading limits
Explaining why a transaction was declined (rule-based, no engineering needed)
General onboarding questions

Resolution target: Same session. No escalation task required.

Tier 2 — Route to Product / Engineering / Finance

Issue requires input or action from a specialized agent. CS cannot resolve independently.

Characteristics:

Requires diagnosis of system behavior or code-level investigation
Requires a product decision or policy clarification
Requires financial or billing action
Reproducible bug or unexpected platform behavior
Issue affects multiple users (pattern, not one-off)

Examples:

User reports transaction stuck in "pending" for > 24h (route to coder via project-manager)
User cannot complete KYC despite correct documentation (route to product-manager)
Billing discrepancy or incorrect fee charged (route to finance-manager)
Feature not working as documented (route to coder)
User reports data not loading or dashboard error (route to coder)
Policy question about what is or isn't allowed on the platform (route to product-manager)

Read the full file on GitHub · 306 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.

today First seen · 306 lines · 38 tokens per session scan A ed4ba0cc3be1

Subscribe to this mod's changes

support-escalation is a skill published in the GitHub repository ProfFroggo/froggo-mission-control (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 2,986 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.

support-escalation next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
support-escalationProfFroggo/froggo-mission-control	Skill	2	6mo ago	Apache-2.0	A	38	Claude Code
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	today	MIT	A	103	Claude Code

froggo-mission-control: Skill for Claude Code