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 skills add jonny-1812/corebee-mcp-skills --skill escalation-managergit clone --depth 1 https://github.com/jonny-1812/corebee-mcp-skillsWrote 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/jonny-1812/corebee-mcp-skills/escalation-manager)<a href="https://agentmods.dev/skills/jonny-1812/corebee-mcp-skills/escalation-manager"><img src="https://agentmods.dev/badge/skills/jonny-1812/corebee-mcp-skills/escalation-manager/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/jonny-1812/corebee-mcp-skills/escalation-manager"><img src="https://agentmods.dev/badge/skills/jonny-1812/corebee-mcp-skills/escalation-manager.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.00055 | $0.01556 |
| Opus 5 | $0.00028 | $0.00778 |
| Sonnet 5 | $0.00011 | $0.00311 |
| Haiku 4.5 | $0.00006 | $0.00156 |
Grade A, and why
escalation-manager 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 12d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Escalation Manager
Handle critical customer conversations from detection through resolution — escalate, assign, respond, and de-escalate with full audit trails.
Workflow Modes
Escalate Specific Conversation
Escalate a known conversation by ID, assigning it to the best available agent and logging the escalation.
- Fetch the conversation using
get_conversationwith the provided conversation ID - Fetch team members using
list_team_membersto find available agents - Evaluate the conversation: read the full thread to understand severity, customer sentiment, and topic
- Select the best agent using the agent selection criteria below
- Assign the conversation using
assign_conversationto the selected agent - Log an escalation note on the contact using
add_contact_notewith the escalation reason, assigned agent, and timestamp - Optionally draft an immediate acknowledgment response — present it to the user for approval before sending via
reply_to_conversation - Present the escalation summary
Scan for Urgent Items
Proactively scan the inbox for conversations that meet escalation criteria and present them for action.
- Fetch all open conversations using
list_conversationswithstatus: "open" - Fetch team members using
list_team_membersto check availability - For each open conversation, evaluate against the escalation criteria below
- For conversations that meet criteria, use
get_conversationto read the full thread and confirm urgency - Present a ranked list of conversations needing escalation, ordered by severity
- Ask the user which conversations to escalate
- For each confirmed escalation, run the Escalate Specific Conversation workflow
De-escalate
Close a resolved escalation, log the resolution, and optionally notify the customer.
- Fetch the conversation using
get_conversationto confirm it is resolved - Verify the customer's issue has been addressed by reviewing the thread
- Log a de-escalation note on the contact using
add_contact_notewith resolution details - Optionally draft a closing message for the customer — present for approval before sending
- Close the conversation using
close_conversation - Present a de-escalation summary with resolution time and outcome
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.
- 12d ago First seen · 124 lines · 55 tokens per session scan A 4052d30f7ef1
escalation-manager is a skill published in the GitHub repository jonny-1812/corebee-mcp-skills (0 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 1,556 once invoked, about $0.0003 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-30.
Other skills, from other repositories
customer-support
Use when a live support ticket needs triage (intent, P1–P4 priority, SLA clock), an on-voice reply, not a raw template, de-escalation of an angry or churn-risk customer, or escalation with a handoff packet. NOT the help-center article it links to (that is technical-writing), a win-back program (retention), or the…
deskcrew-support
Run a customer support desk on DeskCrew. Read new tickets, answer from the knowledge base, and file replies for human approval. Use when handling customer support. Agents can also create and run their own bounty board over x402 with no account (the wallet that pays createboard owns it) and pay answering agents 85% on…
deskcrew-bounty-hunter
Earn USDC by answering bounty support tickets on DeskCrew's open board. Read the board free, buy ticket context over x402, draft an answer, submit it, and get paid 85% of the bounty when a human approves. Pays out on Base, Polygon, Avalanche, Sei, or Solana; on Solana the agent needs zero SOL. Since 08-2026 the wallet…
deskcrew-board-owner
Run your own USDC bounty board and pay AI agents to answer your questions. One x402 payment creates the board (no account, the paying wallet owns it), USDC deposits fund tasks, and approving an answer pays the winning agent 85% automatically on Base, Polygon, Avalanche, Sei, or Solana. Use when asked to delegate work…
Zendesk Automation
Automate customer support workflows with Zendesk ticket management, routing, and analytics.
customer-support-integration
Connect your helpdesk (Gorgias, Zendesk, Intercom) to your store so support agents see full order history and customer details without switching tools.