agentmods.dev

phone-claim-verifier

phone-claim-verifier is a skill for Claude Code, Codex from CALLE-AI/awesome-phone-call-agents. It costs 83 tokens per session (1,731 once invoked), scanned A, original, MIT.

A phone-based record checker that tests claims against information supplied by the person answering. It returns MATCH, MISMATCH, UNCLEAR, or NOCONTACT, and requires the person's exact words to support a clear result.

In plain words
What is it for?
Use it to check clinics, suppliers, community services, contacts, or other phone-reachable records. It helps verify claims such as whether an office accepts a plan or whether a contact is still correct.
Why use it?
Directories and contact lists can become outdated, while an unsupported answer can be mistaken for a fact. This makes uncertainty visible and preserves direct spoken evidence.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 109repo +2 yesterday A scan 83 tokens original MIT

Good fit Use it to check clinics, suppliers, community services, contacts, or other phone-reachable records. It helps verify claims such as whether an office accepts a plan or whether a contact is still correct.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/calle-ai/awesome-phone-call-agents/phone-claim-verifier
View source ↗ CALLE-AI/awesome-phone-call-agents
Install

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.

Any agent
npx skills add CALLE-AI/awesome-phone-call-agents --skill phone-claim-verifier
Clone the repo
git clone --depth 1 https://github.com/CALLE-AI/awesome-phone-call-agents

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for phone-claim-verifier

README.md
[![agentmods](https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/phone-claim-verifier/github.svg)](https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/phone-claim-verifier)
Your own site
<a href="https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/phone-claim-verifier"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/phone-claim-verifier/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.

agentmods 80×15 button for phone-claim-verifier

Your own site · 80×15
<a href="https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/phone-claim-verifier"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/phone-claim-verifier.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 83 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,731 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00083 $0.01731
Opus 5.5 $0.00033 $0.00692
Sonnet 5.5 $0.00017 $0.00346
Haiku 4.5 $0.00008 $0.00173

Measured 1mo ago against content hash 7e0acce98fd3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

phone-claim-verifier 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.

The scan reads SKILL.md. This mod also ships 5 executable files (scripts/_display.py, scripts/_pcv.py, scripts/plan.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/phone-claim-verifier/SKILL.md · 136 lines

How it starts

The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Phone Claim Verifier

Use this skill when the user has a table of records - each with a phone number and one or more claims attached - and wants those claims checked by calling the number and asking.

Examples: "call each clinic in this CSV and confirm they still take the Northline Health plan", "phone these suppliers and check the contact name on file is still right", "verify this community-services directory is still accurate".

The skill is a thin wrapper around CALL-E's one-off call workflow. It does not add backend APIs, provider-side batches, a daemon, or new MCP tools. Two small standard-library scripts do the deterministic work; you (the agent) place the calls and read the transcripts.

The one rule

A MATCH or MISMATCH verdict is only produced when a verbatim quote from a recipient turn supports it. If you cannot copy such a quote out of the transcript, the verdict is UNCLEAR - stated plainly, not as an error. This is enforced in scripts/verdict.py, in code. Read references/evidence-rules.md before resolving any call.

When To Use

  • checking phone-reachable records against claims: does this office accept this plan, is this still the contact, are these hours current, is this address right
  • batch verification where each record has its own phone number and its own asserted facts
  • producing an evidence-backed corrections file a team can act on

When Not To Use

  • placing calls to numbers that are not on a record in the user's own table
  • inferring a phone number, region, timezone, or language - ask the user, do not guess
  • calling third-party numbers the user has not confirmed they are authorised to contact
  • adding a CALL-E backend verification API or a provider-side recurring job
  • resolving a verdict from the recipient's tone or your own inference rather than a quote
  • installing calle globally without the user's explicit approval

Setup

  1. Confirm the user wants real outbound calls placed to the numbers in their table.
  2. Get the records. A CSV with record_id,name,phone,address,region plus one column per claim (values true/false), or a JSON object per record. See examples/providers.csv.
  3. Get or write a claim pack (a JSON file listing the questions to ask and how to read each answer). See references/claim-packs.md and examples/healthcare.json.
  4. Check CALL-E auth. Resolve a CALL-E command or the MCP route the same way other skills in this repository do; the MCP route is https://seleven-mcp-sg.airudder.com/mcp/openagent_oauth.

Read the full file on GitHub · 136 lines

Files

What ships with it

12 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.

Changes

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.

  1. 1mo ago First seen · 136 lines · 83 tokens per session scan A 7e0acce98fd3

Subscribe to this mod's changes

phone-claim-verifier is a skill published in the GitHub repository CALLE-AI/awesome-phone-call-agents (109 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 1,731 once invoked, about $0.0003 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.

Research
Related

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens

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…

vercel/next.js · 123 tokens