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 CALLE-AI/awesome-phone-call-agents --skill emergency-dispatch-cascadegit clone --depth 1 https://github.com/CALLE-AI/awesome-phone-call-agentsWrote 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/calle-ai/awesome-phone-call-agents/emergency-dispatch-cascade)<a href="https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/emergency-dispatch-cascade"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/emergency-dispatch-cascade/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/calle-ai/awesome-phone-call-agents/emergency-dispatch-cascade"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/emergency-dispatch-cascade.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.00061 | $0.02109 |
| Opus 5.5 | $0.00024 | $0.00844 |
| Sonnet 5.5 | $0.00012 | $0.00422 |
| Haiku 4.5 | $0.00006 | $0.00211 |
Grade A, and why
emergency-dispatch-cascade 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.
How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Emergency Dispatch Cascade
Use this skill when a home-service business (plumbing, HVAC, electrical) has one urgent job and a roster of on-call technicians, and only one of them should end up booked on it. It is a cascade, not a broadcast: technicians are rung one at a time, in the order the business gives, and the moment one accepts, the rest are never called. The skill then closes the loop by calling the customer back with the technician's name and ETA — turning a job that would otherwise wait for a human dispatcher into a booked, billable appointment within minutes.
This skill does not add a CALL-E backend queue, a provider-side campaign, a daemon, or new MCP tools. It sequences the existing one-off CALL-E call workflow twice: once per technician cascade, once for the customer confirmation.
When To Use
Use this skill for:
- an incoming non-life-threatening home-service emergency (burst pipe, no heat, power outage in one unit, water heater failure) that needs a technician dispatched now, not scheduled for next week
- a roster of on-call technicians where calling all of them at once would risk double-booking the job
- closing the loop with the customer once a technician has accepted, so they are not left waiting to hear whether anyone is coming
When Not To Use
Do not use this skill to:
- handle a life-threatening emergency — gas leaks, fire, carbon monoxide, electrical arcing, flooding that endangers people, or any medical emergency. Those callers must be told to contact 911 or local emergency services; this skill must refuse to run and say so instead of dispatching a technician
- negotiate price, warranty terms, or liability on the call; the goal states the job and asks for availability and ETA only
- broadcast the same job to every technician at once — that is a campaign, not a cascade, and this skill refuses to run calls in parallel
- decide on the agent's own authority what an unclear technician answer meant
- call a technician who is not on the roster the business supplied, or a customer number the business has not confirmed is correct for this job
- guess phone numbers, country codes, timezones, languages, or regions
- retry a technician who has already declined
- keep dialling technicians after the business's cutoff for same-day dispatch
What ships with it
4 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.
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.
- 1mo ago First seen · 171 lines · 61 tokens per session scan A cf0d08df7ca6
emergency-dispatch-cascade is a skill published in the GitHub repository CALLE-AI/awesome-phone-call-agents (109 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 2,109 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-09-16.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…