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 urgent-help-escalation-callgit 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/urgent-help-escalation-call)<a href="https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/urgent-help-escalation-call"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/urgent-help-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.
<a href="https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/urgent-help-escalation-call"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/urgent-help-escalation-call.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.00093 | $0.02150 |
| Opus 5 | $0.00046 | $0.01075 |
| Sonnet 5 | $0.00019 | $0.00430 |
| Haiku 4.5 | $0.00009 | $0.00215 |
Grade A, and why
urgent-help-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 today.
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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Urgent Help Escalation Call
Use this skill when software has learned that someone needs a human, and a notification is not good enough.
An in-app alert is only as good as somebody looking at a screen. The moments when that assumption fails are exactly the moments the alert exists for: the middle of the night, a shower, a meeting, a commute. A ringing phone is the one channel that reliably interrupts.
This skill is the bridge. One trigger, one call, one clear answer about whether it landed.
The two people
Getting this wrong is the failure mode that matters most, so name them separately in your own code:
| Who | Role | |
|---|---|---|
| Subject | the vulnerable person | asked for help; is never called by this skill |
| Recipient | the carer, responder, or next of kin | the one whose phone rings |
Dialling the subject instead of the recipient means telling a frightened person that a frightened person needs help. Keep the two numbers in separate fields, label them unambiguously in any UI, and validate them separately.
When To Use
- panic buttons and help buttons in apps used by vulnerable people
- lone-worker duress alarms
- fall detection, inactivity timeouts, or bed-exit alerts
- care-home call bells that need to reach staff who are not at a station
- post-discharge deterioration flags
- any in-app urgent signal where "they will see the notification" is a bad bet
When Not To Use
Do not use this skill to:
- replace emergency services — see Emergencies
- call the subject themselves, for any reason
- deliver clinical detail, triage, or advice by phone
- send routine or digest notifications; this is for urgent signals only
- escalate something the subject did not actually ask for, without saying so
- call a responder who has not agreed to be called
Required Fields
Ask for anything missing. Never infer these:
| Field | Notes |
|---|---|
recipient_phone |
E.164. The responder's number, never the subject's. Validate; never guess a country code. |
subject_name |
What the responder should be told, e.g. "Eleanor". |
triggered_at |
When the request happened, so the call can say when rather than "just now". |
recipient_name |
Optional but strongly preferred — being addressed by name at 3am is worth a lot. |
region |
Optional. Chosen, not inferred — it decides which line the call comes from. |
What ships with it
8 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.
- today First seen · 205 lines · 93 tokens per session scan A 2ee3bbab5029
urgent-help-escalation-call is a skill published in the GitHub repository CALLE-AI/awesome-phone-call-agents (88 stars, last pushed yesterday), licensed MIT. It adds 93 tokens to every session and 2,150 once invoked, about $0.0005 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-09-12.
Other skills, from other repositories
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
aws-sdk-java-v2-core
Provides AWS SDK for Java 2.x client configuration, credential resolution, HTTP client tuning, timeout, retry, and testing patterns. Use when creating or hardening AWS service clients, wiring Spring Boot beans, debugging auth or region issues, or choosing sync vs async SDK usage.
migrate-segw-to-rap
Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…