provenance-grade

provenance-grade is a skill for Claude Code, Codex from CALLE-AI/awesome-phone-call-agents. It costs 37 tokens per session (2,337 once invoked), scanned A, original, MIT.

A transcript-based grading step that labels extracted phone-call facts as verified, asserted, or assumed. It also keeps the exact passage that supports each label and does not place calls itself.

In plain words
What is it for?
Use it after a completed call to assess extracted fields and retain their supporting transcript text. It can also check a task before dispatch, but it does not dial phones or make network requests.
Why use it?
The same answer can be carefully checked or merely guessed by the person speaking. This distinguishes the strength of the source's knowledge before an automated workflow relies on the extracted value.

Skill for Claude CodeCodex

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

Good fit Use it after a completed call to assess extracted fields and retain their supporting transcript text. It can also check a task before dispatch, but it does not dial phones or make network requests.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/provenance-grade"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/provenance-grade.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,337 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.00037 $0.02337
Opus 5.5 $0.00015 $0.00935
Sonnet 5.5 $0.00007 $0.00467
Haiku 4.5 $0.00004 $0.00234

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

Security

Grade A, and why

provenance-grade 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 18 executable files (scripts/eval.ts, scripts/fixtures.ts, scripts/grade.ts, …), 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/provenance-grade/SKILL.md · 207 lines

How it starts

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

provenance-grade

Every phone agent extracts what was said and throws away how the speaker knew it.

Speech carries the speaker's epistemic state; text hides it. Structured extraction throws that signal away. This skill puts it back: it reads recipients[i].attempts[j].transcript_turns from a completed CALL-E call and attaches a knowledge grade to every extracted field, with the exact transcript span that supports it.

This skill never places calls: it lints a task before a host dispatches it and grades a transcript after a call has completed. It contains no dialing code, no phone numbers, and no network calls of any kind.

Two calls can both answer "Tuesday." In one, the person said "hold on, let me check", went quiet for eleven seconds, and came back with "Tuesday — we're holding eleven units at the Bhiwandi warehouse." In the other, they said "should be Tuesday" half a second after the question. Same extracted value. Completely different knowledge. The first is verified; the second is assumed — and if your workflow auto-commits on the second one, the extraction was correct and the answer was still wrong.

Why this is not a duplicate of anything in this repo

CALL-E already returns completion_confidence — but by its own documentation that is confidence that the task reached a clear end state, explicitly not confidence in the quality of the business answer. That is a documented, self-acknowledged gap, and this skill fills exactly it.

Against the other skills here: call-summarizer summarises after the fact. voice-preflight checks audio before the call. linecanary monitors line health. Nothing grades the epistemic basis of a spoken claim.

The grades

Grade Meaning
verified The heuristic detects a lookup pause or explicit check language, plus an unrequested corroborating specific, plus read-back compliance where requested. This label is not proof that a lookup occurred or that the answer is true.
asserted Answered directly and cleanly, but nothing established where the value came from.
assumed Hedged, deferred, misaligned with the question, or a bare round number. The call did not establish this value.
unstated The field never appeared in the transcript (voicemail, IVR, unanswered question). Never a grade — there is nothing to grade.

Read the full file on GitHub · 207 lines

Files

What ships with it

53 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 · 207 lines · 37 tokens per session scan A 00084c558dc4

Subscribe to this mod's changes

provenance-grade is a skill published in the GitHub repository CALLE-AI/awesome-phone-call-agents (109 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 2,337 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.

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