Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sun2443/designer-skillsnpx agentmods add skills/sun2443/designer-skills/customer-escalationWrote 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/sun2443/designer-skills/customer-escalation)<a href="https://agentmods.dev/skills/sun2443/designer-skills/customer-escalation"><img src="https://agentmods.dev/badge/skills/sun2443/designer-skills/customer-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.
<a href="https://agentmods.dev/skills/sun2443/designer-skills/customer-escalation"><img src="https://agentmods.dev/badge/skills/sun2443/designer-skills/customer-escalation.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.00054 | $0.02402 |
| Opus 5.5 | $0.00022 | $0.00961 |
| Sonnet 5.5 | $0.00011 | $0.00480 |
| Haiku 4.5 | $0.00005 | $0.00240 |
Grade A, and why
customer-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 13d 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.
This is a copy
100% identical to customer-escalation — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/customer-escalation
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Package a support issue into a structured escalation brief for engineering, product, or leadership. Gathers context, structures reproduction steps, assesses business impact, and identifies the right escalation target.
Usage
/customer-escalation <issue description> [customer name or account]
Examples:
/customer-escalation API returning 500 errors intermittently for Acme Corp/customer-escalation Data export is missing rows — 3 customers reported this week/customer-escalation SSO login loop affecting all Enterprise customers/customer-escalation Customer threatening to churn over missing audit log feature
Workflow
1. Understand the Issue
Parse the input and determine:
- What's broken or needed: The core technical or product issue
- Who's affected: Specific customer(s), segment, or all users
- How long: When did this start? How long has the customer been waiting?
- What's been tried: Any troubleshooting or workarounds attempted
- Why escalate now: What makes this need attention beyond normal support
Use the "When to Escalate vs. Handle in Support" criteria below to confirm this warrants escalation.
2. Gather Context
Pull together relevant information from available sources:
- ~~support platform: Related tickets, timeline of communications, previous troubleshooting
- ~~CRM (if connected): Account details, key contacts, previous escalations
- ~~chat: Internal discussions about this issue, similar reports from other customers
- ~~project tracker (if connected): Related bug reports or feature requests, engineering status
- ~~knowledge base: Known issues or workarounds, relevant documentation
3. Assess Business Impact
Using the impact dimensions below, quantify:
- Breadth: How many customers/users affected? Growing?
- Depth: Blocked vs. inconvenienced?
- Duration: How long has this been going on?
- Revenue: ARR at risk? Pending deals affected?
- Time pressure: Hard deadline?
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.
- 13d ago First seen · 249 lines · 54 tokens per session scan A 90c33574a413
customer-escalation is a skill published in the GitHub repository sun2443/designer-skills (0 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 54 tokens to every session and 2,402 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to customer-escalation, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…