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 exception-resolvergit 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/exception-resolver)<a href="https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/exception-resolver"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/exception-resolver/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/exception-resolver"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/exception-resolver.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.01206 |
| Opus 5 | $0.00026 | $0.00603 |
| Sonnet 5 | $0.00011 | $0.00241 |
| Haiku 4.5 | $0.00005 | $0.00121 |
Grade A, and why
exception-resolver 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 11d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exception Resolver
Resolve operational exceptions by gathering missing information through an authorized CALL-E phone conversation and returning a structured result for human approval.
Purpose
Use this skill when an AI agent detects a supported operational exception that cannot be resolved from available system data and requires information from an authorized person.
Read references/resolution-workflow.md for the detailed exception-resolution workflow and safety requirements.
Workflow
- Identify the operational exception and available context.
- Determine what information is missing.
- Establish explicit per-run intent for the proposed call.
- Confirm the destination is an authorized contact and the phone number is valid strict E.164 format.
- Check that the call is not a duplicate and that no unresolved prior call already covers the same exception and intent.
- Decide whether a phone call is necessary.
- Place a CALL-E call only after the required safety checks pass.
- Gather the information required to understand the exception.
- Treat uncertain, incomplete, failed, cancelled, refused, or ambiguous outcomes as unresolved.
- Return the call outcome as structured operational data with masked phone output.
- Present the proposed resolution to a human decision-maker.
- Apply the resolution only after human approval.
Per-run intent
Before placing a call, the agent MUST have explicit intent for that specific run.
The intent must identify:
- the exception being resolved
- the operational objective of the call
- the authorized party or role to contact
- the information the agent is permitted to request or disclose
- the expected resolution or decision
- whether the call may create an external side effect
Do not infer permission to call merely because an exception exists.
If intent is missing, ambiguous, unauthorized, or outside this skill's supported workflow, do not place the call.
Phone-number requirements
Outbound phone numbers MUST be supplied in strict E.164 format.
What ships with it
3 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.
- 11d ago First seen · 180 lines · 53 tokens per session scan A c87603ae7817
exception-resolver is a skill published in the GitHub repository CALLE-AI/awesome-phone-call-agents (85 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 1,206 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…