call-review

call-review is a skill for Claude Code, Codex from CALLE-AI/awesome-phone-call-agents. It costs 72 tokens per session (831 once invoked), scanned A, original, MIT.

A review process for checking a finished CALL-E call before its structured result is used. It compares result fields with the transcript, checks timing and silences, and looks for missing AI disclosure, ignored stop requests, or unsafe sensitive-data readbacks.

In plain words
What is it for?
Use it to approve, reject, or send finished calls to a human reviewer, either one at a time or in batches.
Why use it?
It can catch unsupported or unsafe call results before they update records, close tickets, make bookings, or trigger payments.

Skill for Claude CodeCodex

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

Good fit Use it to approve, reject, or send finished calls to a human reviewer, either one at a time or in batches.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/calle-ai/awesome-phone-call-agents/call-review
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 call-review
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 call-review

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/call-review"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/call-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 831 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.00072 $0.00831
Opus 5 $0.00036 $0.00415
Sonnet 5 $0.00014 $0.00166
Haiku 4.5 $0.00007 $0.00083

Measured today against content hash 325ec7624ca7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

call-review 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.

skills/call-review/SKILL.md · 50 lines

How it starts

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

Call Review

Use this skill after a CALL-E call task has reached a terminal status and before its structured_result is used for anything that matters (booking, closing a ticket, updating a record, paying).

When To Use

  • a call task reports task_completed: true and you are about to act on the result
  • a batch of calls finished and you want to know which results can be trusted without reading every transcript
  • a reviewer asks "did the agent say it was an AI" or "why was this call slow"

When Not To Use

  • to decide whether to place a call (that is a consent and authorization question; see the safety references in this repository)
  • as the only check on an irreversible or financial action; the verdict is advice for a human disposition
  • on a call that has not reached a terminal status

Setup

Fetch the terminal snapshot with the official SDK or CLI (read-only):

calle calls get <call_id>   # or: client.calls.get(call_id)

Optionally run the console in this repository (apps/web/call-review-console) which performs every check below and records the disposition.

Workflow

  1. Status first. status must be completed. failed, cancelled or a failure_code on the attempt is an automatic reject; nothing else needs checking.
  2. Structured result vs. transcript. For every leaf field, find the turn that supports the value. Numbers must be spoken (a reported 9am needs "9", "nine", "9 a.m." in a callee turn). A value with no supporting turn is an unsupported claim; one unsupported claim is a reject. Boolean and enum fields (yes/no/confirmed) need a turn read in context, not a keyword hit.
  3. Timing. From transcript_turns[].offset_seconds: response latency = agent turn start − previous callee turn start. Report p50 and p95; p95 above 6 s or two or more overlaps (a turn starting before the previous one) is needs_human. Silences over 4 s are listed with their position.
  4. Compliance. The agent must disclose it is an AI in its turns, ideally the first. A callee stop or opt-out request ("stop calling", "remove my number", "don't call again") must be the last exchange; any agent turn after it that is not a goodbye is a reject. Card, account or ID-like numbers read aloud by the agent are a reject.
  5. Verdict. approve only when every field is supported or read-and-confirmed, timing is within limits and compliance passes. Otherwise needs_human (timing, unreadable fields) or reject (failed call, unsupported claim, ignored stop, no disclosure, sensitive readback). Write the reasons in one line each.
  6. Disposition. Record who reviewed, when, the verdict and a note. Never edit the call's result to make it pass.

Read the full file on GitHub · 50 lines

Files

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.

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. today First seen · 50 lines · 72 tokens per session scan A 325ec7624ca7

Subscribe to this mod's changes

call-review is a skill published in the GitHub repository CALLE-AI/awesome-phone-call-agents (88 stars, last pushed yesterday), licensed MIT. It adds 72 tokens to every session and 831 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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