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 agentmods add commands/fergupa/claude_plugins/escalategit clone --depth 1 https://github.com/fergupa/claude_pluginsWhat 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 | $0.00013 | $0.00961 |
| Opus 5 | $0.00006 | $0.00481 |
| Sonnet 5 | $0.00003 | $0.00192 |
| Haiku 4.5 | $0.00001 | $0.00096 |
Grade A, and why
escalate 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 2d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Escalate
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
/escalate <issue description> [customer name or account]
Examples:
/escalate API returning 500 errors intermittently for Acme Corp/escalate Data export is missing rows — 3 customers reported this week/escalate SSO login loop affecting all Enterprise customers/escalate 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 from the escalation skill 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 from the escalation skill, 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.
- 2d ago First seen · 116 lines · 13 tokens per session scan A 94814e5af4e1
escalate is a command published in the GitHub repository fergupa/claude_plugins (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 961 once invoked, about $0.0001 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.