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 human-context-handoffgit 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/human-context-handoff)<a href="https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/human-context-handoff"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/human-context-handoff/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/human-context-handoff"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/human-context-handoff.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.00056 | $0.01100 |
| Opus 5 | $0.00028 | $0.00550 |
| Sonnet 5 | $0.00011 | $0.00220 |
| Haiku 4.5 | $0.00006 | $0.00110 |
Grade A, and why
human-context-handoff 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 13d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Human Context Handoff
Use this skill when useful agent work is blocked by one specific piece of context that only an enrolled human can provide and that person is not available in the current channel.
The handoff is asynchronous. A live request returns a durable request ID quickly. The host stores that ID and polls for a terminal result instead of holding one tool request open for the length of a phone call.
When to use
- A product or workflow choice has two to five bounded options.
- An operations alert needs a human preference, such as pause, escalate, or continue monitoring.
- The missing answer materially changes the next useful agent action.
- The intended recipient was previously verified, consented to calls, and is allowed by the user's current calling policy.
When not to use
- The user is available in the current conversation. Ask there first.
- The question requests a password, one-time code, credential, payment data, private key, or other secret.
- The answer would be treated as identity proof or as authorization for an irreversible, regulated, legal, medical, financial, or emergency action.
- The context cannot be reduced to one short question with bounded choices.
- The recipient declined, the request expired, or the person could not be reached. Do not call again automatically to seek a different outcome.
Required inputs
Prepare these fields before any live request:
- a short task title;
- a minimized context summary;
- one question;
- two to five choices with stable machine-readable IDs;
- the verified recipient label or identifier, never a raw number in agent output;
- what the agent will do with each answer;
- an expiry time;
- one stable idempotency key for the logical question.
If any field is missing or ambiguous, stop and ask in the current channel.
Preview first
Always show a no-call preview before a live handoff unless the user has already approved an account policy that explicitly covers this exact class of call. The preview must include:
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.
- 13d ago First seen · 121 lines · 56 tokens per session scan A 0eff6e929ae2
human-context-handoff is a skill published in the GitHub repository CALLE-AI/awesome-phone-call-agents (88 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 1,100 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…