incident-escalation-call

incident-escalation-call is a skill for Claude Code, Codex from CALLE-AI/awesome-phone-call-agents. It costs 75 tokens per session (1,359 once invoked), scanned A, original, MIT.

A phone-based incident escalation process for getting a named human owner and an estimated response time during a production problem.

In plain words
What is it for?
Use it to call on-call engineers in order, collect an owner and ETA, verify the acknowledgement through another channel, and return a result with an audit ledger.
Why use it?
A sent alert does not prove that anyone heard it or accepted responsibility, especially when the on-call engineer is away from a keyboard.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to call on-call engineers in order, collect an owner and ETA, verify the acknowledgement through another channel, and return a result with an audit ledger.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/calle-ai/awesome-phone-call-agents/incident-escalation-call
Install

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.

Any agent
npx skills add CALLE-AI/awesome-phone-call-agents --skill incident-escalation-call
Clone the repo
git clone --depth 1 https://github.com/CALLE-AI/awesome-phone-call-agents

Made for: Claude Code, Codex.

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 incident-escalation-call

README.md
[![agentmods](https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/incident-escalation-call/github.svg)](https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/incident-escalation-call)
Your own site
<a href="https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/incident-escalation-call"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/incident-escalation-call/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 incident-escalation-call

Your own site · 80×15
<a href="https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/incident-escalation-call"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/incident-escalation-call.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,359 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00075 $0.01359
Opus 5.5 $0.00030 $0.00544
Sonnet 5.5 $0.00015 $0.00272
Haiku 4.5 $0.00007 $0.00136

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

Security

Grade A, and why

incident-escalation-call 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 1mo 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.

skills/incident-escalation-call/SKILL.md · 115 lines

How it starts

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

Incident Escalation Call

Use this skill when an incident needs a human owner and "notification sent" is not evidence that anybody heard it.

It does not invent an escalation mechanism. It drives the runnable ringdown app, which resolves who is on call right now, places one CALL-E call per person in ladder order, accepts only a commitment with an owner and an ETA, re-derives that acknowledgement from the raw transcript over MCP — a second transport the writing path never touched — and returns an exit code plus a hash-chained ledger.

When to use

  • A monitoring alert, a failed deploy or a user-facing outage needs a named owner with a spoken commitment, and the on-call rotation is defined.
  • The on-call engineer is asleep or away from a keyboard, which is exactly when a phone call beats a push notification, an email or a chat message.
  • The user asked to page, escalate or wake up whoever is on call.

When not to use

  • The user is the on-call engineer and is already in this conversation. Tell them here.
  • You do not have a rotation file with enrolled contacts in E.164 form and on-call windows that cover this moment. Do not guess a number, a country code, a region or a name.
  • Anything medical, legal, financial advice or an emergency. See references/safety.md.
  • Ringing somebody again after an explicit decline. A no is final for the run.

How it works

  1. You write an incident file — id, title, severity, service, summary, the ladder of scopes, the acknowledgement policy — or produce one from a raw alert payload with adapt. The rotation file lists who covers each scope and when.
  2. You run preview and show the user the resolved ladder and the exact call task. Preview opens no socket and reads no credentials.
  3. On the user's go-ahead you run it live. The app calls one person at a time, top of the ladder first. An acknowledgement needs an owner and an ETA spoken by the person who answered; a bare "yeah, sure" does not advance anything and the ladder moves on.
  4. After the ladder settles, the app re-reads the calls over MCP and checks the recorded verdict against transcripts fetched on that second channel.
  5. You read the exit code. Nothing else counts as an acknowledgement.

Read the full file on GitHub · 115 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 1mo ago Changed · +5 lines aa77fff9ad78
  2. 2mo ago First seen · 110 lines · 75 tokens per session scan A 90ed0eaad538

Subscribe to this mod's changes

incident-escalation-call is a skill published in the GitHub repository CALLE-AI/awesome-phone-call-agents (112 stars, last pushed 4d ago), licensed MIT. It adds 75 tokens to every session and 1,359 once invoked, about $0.0003 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-08-30.

Related

incident-escalation-call compared with skills from other repositories

incident-escalation-call next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
incident-escalation-callCALLE-AI/awesome-phone-call-agentsSkill1124d agoMITA75Claude Code, Codex
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k2d agoMITA200Claude Code, Codex
playwright-climicrosoft/playwrightSkill100kyesterdayApache-2.0A19Claude Code
browser-automationopenclaw/openclawSkill394ktodayMITA36Claude Code
systematic-debuggingobra/superpowersSkill315k5d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code