call-closing-sequence-auditor

call-closing-sequence-auditor is a skill for Claude Code, Codex from CALLE-AI/awesome-phone-call-agents. It costs 82 tokens per session (1,168 once invoked), scanned A, original, MIT.

A transcript checker for the ending of a phone call. It looks for a summary, agreed next steps, a completed goodbye, unanswered questions, and new business raised after the farewell.

In plain words
What is it for?
Use it after completed calls or in quality-review pipelines to find calls needing a clearer closing or follow-up.
Why use it?
It finds endings that leave people unsure what happens next or with unresolved questions. It evaluates the structure of the ending, not the caller’s satisfaction.

Skill for Claude CodeCodex

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

Good fit Use it after completed calls or in quality-review pipelines to find calls needing a clearer closing or follow-up.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/call-closing-sequence-auditor"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/call-closing-sequence-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 82 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,168 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.00082 $0.01168
Opus 5.5 $0.00033 $0.00467
Sonnet 5.5 $0.00016 $0.00234
Haiku 4.5 $0.00008 $0.00117

Measured 16d ago against content hash 652949a49632, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

call-closing-sequence-auditor 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 16d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/closing_sequence_auditor.py, scripts/test_closing_sequence_auditor.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/call-closing-sequence-auditor/SKILL.md · 104 lines

How it starts

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

call-closing-sequence-auditor

The last twenty seconds are what the person repeats to their family. The body of the call is forgotten; the ending is the memory.

Closings are not hanging up. In conversation analysis they are an organized sequence the two parties co-produce: a pre-closing summary of what was settled, an arrangement for what happens next, a mutually exchanged goodbye. A call that stops short of that sequence leaves the person with unanswered questions, or with business introduced after the farewell that nobody can act on. This skill grades the shape of that final sequence on a finished CALL-E transcript.

When To Use

  • after any outcome-bearing CALL-E call, before writing up the results
  • in QA pipelines, to batch-scan finished transcripts for endings that need a follow-up touch
  • before replaying calls with a tighter scripted closing, to compare ending shape across runs

When Not To Use

  • as a satisfaction or call-quality score; the card measures sequence shape, not how the person felt
  • when the callee hung up mid-flow; truncation by the caller is a legitimate ending and is not the agent's failure
  • during a call; strictly post-call analysis plus pre-call goal crafting
  • on non-English transcripts; every lexicon is English-only

Workflow

Audit a finished call

python3 scripts/closing_sequence_auditor.py analyze \
  --transcript path/to/call-result.json

Reads the real get_call_run result shape ({status, result: {transcript}}) or the flat fixture shape used by sibling skill fixtures. The closing window is the last 6 turns (the whole transcript if shorter); the six checks are:

  • summary_present: an agent turn in the window that marks a summary ("just to confirm", "to recap", ...) or states a confirm verb ("booked", "confirmed", ...) backed by a concrete value
  • arrangement_present: an agent move that settles the next step ("we'll send", "you'll receive", "no further action", ...)
  • terminal_exchange_complete: the agent said a farewell in the window and the callee said one anywhere after the first turn
  • dangling_question: the callee's last "?" received only farewells - or nothing at all
  • post_closing_business: the agent introduced values or questions after its own first farewell
  • abrupt_end: no agent farewell in the window and the call stops on a question or a plain non-farewell turn

Read the full file on GitHub · 104 lines

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. 16d ago First seen · 104 lines · 82 tokens per session scan A 652949a49632

Subscribe to this mod's changes

call-closing-sequence-auditor is a skill published in the GitHub repository CALLE-AI/awesome-phone-call-agents (109 stars, last pushed yesterday), licensed MIT. It adds 82 tokens to every session and 1,168 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-10-04.

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