call-state-reconciler

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

A tool for determining what really happened during a CALL-E phone call by comparing its task, attempts, and event history. It separates how the call ended, whether the task was completed, and whether a person actually answered.

In plain words
What is it for?
Use it before acting on call results, when calls remain unresolved, or when call statuses and event records disagree.
Why use it?
A call can report completion even when it reached voicemail, so relying on one status can cause a booking, payment, or record update to happen incorrectly.

Skill for Claude CodeCodex

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

Good fit Use it before acting on call results, when calls remain unresolved, or when call statuses and event records disagree.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/call-state-reconciler"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/call-state-reconciler.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,228 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.00068 $0.01228
Opus 5 $0.00034 $0.00614
Sonnet 5 $0.00014 $0.00246
Haiku 4.5 $0.00007 $0.00123

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

Security

Grade A, and why

call-state-reconciler 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-state-reconciler/SKILL.md · 123 lines

How it starts

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

Call State Reconciler

A finished call hands you a status word, a task_completed boolean and a confidence score. Three answers jammed into a shape that looks like one, and the one everybody branches on is task_completed.

It comes back true for a voicemail box. The recording picks up, the agent asks its question into the tone, and the call ends completed with a schema-valid result and a high score. Nothing in that payload is a lie. There is simply no field in it that says a person was ever on the line.

This skill covers reading a call properly: how it ended, whether the job got done, and whether the answer came from anybody speaking. Three separate questions, answered separately, each one carrying the field it was read from.

When to use it

Use it before a call result moves anything in a system of record. Booking, dispatching, charging, closing a ticket, marking a lead dead.

Use it when a call will not settle, or when you are looking at a batch of calls and need to know which ones need a person today.

Use it when two signals disagree: the call task says one thing and its recipient says another, or the attempt timing does not match the event stream.

Do not use it on a call nobody acts on automatically. A call that produces a note for a human to read has no branch to get wrong, and this is overhead.

The one field that changes everything

The Calls API carries no answered-by field. The calls guide says so directly and tells you to define the classification yourself in a per-recipient result schema:

{
  "type": "object",
  "required": ["answered_by"],
  "properties": {
    "answered_by": {
      "type": "string",
      "enum": ["human", "ivr", "voicemail", "unknown"],
      "description": "Classify the final endpoint. If an IVR transfers the call to a person, use human."
    }
  },
  "additionalProperties": false
}

Send that and the ending stops being a guess. Without it the honest answer to "did a person pick up" is that nothing in the payload establishes one, which is true and not much use to anybody.

Read the full file on GitHub · 123 lines

Files

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.

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 · 123 lines · 68 tokens per session scan A 5ea21c5979c4

Subscribe to this mod's changes

call-state-reconciler is a skill published in the GitHub repository CALLE-AI/awesome-phone-call-agents (88 stars, last pushed yesterday), licensed MIT. It adds 68 tokens to every session and 1,228 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-09-12.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens