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 opportunity-verification-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/opportunity-verification-call)<a href="https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/opportunity-verification-call"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/opportunity-verification-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/opportunity-verification-call"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/opportunity-verification-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.00034 | $0.00531 |
| Opus 5.5 | $0.00014 | $0.00212 |
| Sonnet 5.5 | $0.00007 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
opportunity-verification-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.
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Opportunity Verification Call
Purpose
A focused CALL-E Agent Skill for verifying a listed local employment or gig opportunity before a person incurs downstream costs (travel, printing, airtime, or application effort).
Unlike skills that screen candidates or verify digital bounties (e.g., bounty-screening-call), this skill focuses on the physical-world cost of uncertainty in local gig economies. It asks: Is the opportunity still open? Where is it? What is the compensation and application path?
The workflow takes an existing opportunity plus an explicitly approved contact, prepares a bounded verification task, and uses CALL-E to gather structured phone evidence.
This is an instructional reference, not an included CALL-E adapter or host runtime. Read the safety rules before use and follow the fictional example for a no-call walkthrough.
Host execution sequence
- Start with a no-call preview: collect the opportunity ID, bounded questions, and an operator-authorized contact. Validate the private destination as E.164 and show only a masked number in the preview.
- Obtain explicit approval for this one call and its questions. The host must supply its supported CALL-E integration, secure credential storage, and the same stable intent key for this opportunity/contact task where supported. If the host cannot meet the safety rules, remain in preview mode.
- Submit at most one call for that approved intent. Record its provider ID and status in private host state; do not create a recurring schedule.
- If submission or completion is ambiguous, mark it
UNKNOWNand stop. Do not automatically redial, create a fresh intent, or take a conflicting downstream action. A human must reconcile the existing provider state first. - Present a masked, advisory receipt separating call status, transcript evidence, and extracted claims. A person decides whether to act on the opportunity; this skill does not establish employer identity or guarantee an offer is valid.
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.
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 · 45 lines · 34 tokens per session scan A e5af7ca7f5e8
opportunity-verification-call is a skill published in the GitHub repository CALLE-AI/awesome-phone-call-agents (109 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 531 once invoked, about $0.0001 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
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…