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.
npx skills add CALLE-AI/awesome-phone-call-agents --skill call-goal-drift-auditorgit clone --depth 1 https://github.com/CALLE-AI/awesome-phone-call-agentsWrote 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.
[](https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/call-goal-drift-auditor)<a href="https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/call-goal-drift-auditor"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/call-goal-drift-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.
<a href="https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/call-goal-drift-auditor"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/call-goal-drift-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00080 | $0.01363 |
| Opus 5.5 | $0.00032 | $0.00545 |
| Sonnet 5.5 | $0.00016 | $0.00273 |
| Haiku 4.5 | $0.00008 | $0.00136 |
Grade A, and why
call-goal-drift-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 25d ago.
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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
call-goal-drift-auditor
An agent told to confirm an appointment that ends up selling whitening packages has drifted. Nobody noticed. Until now.
Every CALL-E call starts with a goal. But calls are dynamic: a curious
callee, an ambitious agent script, or a distraction tangent can pull the
conversation far from the stated objective. Without post-call auditing,
nobody knows the goal was never really achieved — or that three agent turns
were spent on topics that were explicitly out of scope.
This skill reads the finished transcript alongside the original goal text, extracts content keywords, measures per-turn on-topic ratio, detects off-topic spans, and reports whether the goal appears achieved in the closing confirmation. It also generates a tighter, bounded goal with explicit scope-limiting instructions for the next call.
When To Use
- after any CALL-E call where scope discipline matters
- when a call goal is narrow and violations are measurable (appointment confirmation, payment verification, consent capture)
- as part of a QA pipeline to detect systematic agent scope creep
- before replaying a failed or incomplete call with tighter instructions
When Not To Use
- without a goal file; drift is measured against the goal text and the CLI requires it
- when the goal is intentionally broad ("assist the caller as needed")
- as a legal or compliance ruling; it is heuristic and advisory only
- for non-English transcripts; keyword extraction is English-only
Workflow
Audit a finished call
python3 scripts/goal_drift_auditor.py analyze \
--transcript path/to/call-result.json \
--goal-file path/to/goal.txt
Reads the real get_call_run result shape or flat fixture shape.
The goal file may be plain text or a JSON object with a goal,
task, or objective key. Emits a drift card:
goal_keywords[]: content words extracted from the goal (sorted, 4+ char, non-stop-word)agent_turn_count/on_topic_turn_count/on_topic_ratiooff_topic_spans[]: each span of ≥ 2 consecutive agent turns without goal keywords, withstart_turn_index,length_in_agent_turns, and PII-maskedfirst_off_topic_evidencegoal_achieved:trueif goal keywords appear with a confirmation phrase in any of the last 4 agent turnsverdict:ON_TRACK/MILD_DRIFT/SIGNIFICANT_DRIFT/GOAL_NOT_ACHIEVED, plusunclearpathsrecommended_action:no_action_required,monitor_and_consider_tighter_goal, orretry_with_tighter_goalwith guidance
What ships with it
7 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.
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.
- 25d ago First seen · 107 lines · 80 tokens per session scan A 760762c09d5a
call-goal-drift-auditor is a skill published in the GitHub repository CALLE-AI/awesome-phone-call-agents (109 stars, last pushed yesterday), licensed MIT. It adds 80 tokens to every session and 1,363 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-25.
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…
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…
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.
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…
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…
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…