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-cognitive-load-monitorgit 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-cognitive-load-monitor)<a href="https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/call-cognitive-load-monitor"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/call-cognitive-load-monitor/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-cognitive-load-monitor"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/call-cognitive-load-monitor.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.00040 | $0.02250 |
| Opus 5.5 | $0.00016 | $0.00900 |
| Sonnet 5.5 | $0.00008 | $0.00450 |
| Haiku 4.5 | $0.00004 | $0.00225 |
Grade A, and why
call-cognitive-load-monitor 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.
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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
call-cognitive-load-monitor
Detect when your caller is overwhelmed — before it costs you the call.
This skill analyzes supplied text for heuristic confusion markers and conversational proxies. It does not measure acoustics, administer a cognitive assessment, or establish consent validity. Reports and suggested script changes require human review; no live integration, message sending or follow-up call is performed.
Why This Skill Exists
Most call-centre quality tools measure whether the agent performed well. This skill measures whether the caller was able to process what was said. When cognitive load peaks — especially at closing, where consent and commitment are given — the validity of that interaction is at risk.
Advisory scope: A CONSENT_AT_RISK label is a suggestion for human review, not a regulatory finding or authorization for a follow-up call. No label establishes that consent is valid or invalid.
Research Scope
The weights and thresholds are unvalidated demonstration choices, not a reproduction of a published acoustic model. Background and claim limitations: references/research-papers.md.
Quick Start
python3 scripts/monitor_cognitive_load.py \
--transcript path/to/transcript.json \
--dry-run \
--out /tmp/load_report.json
Validate output schema
python3 scripts/validate_load_report.py --report /tmp/load_report.json
Input
Standard CALL-E transcript — same two formats as other skills:
Format A — array of turns:
[
{"role": "agent", "text": "Under the terms of sub-clause 4(b)(ii) of the agreement..."},
{"role": "callee", "text": "Sorry, could you say that again? I'm not following."},
{"role": "agent", "text": "Of course. Regarding the billing section specifically..."},
{"role": "callee", "text": "I still don't understand. What does that mean for me?"}
]
Output — Overload Report
{
"call_id": "calle-001",
"analysis_timestamp": "2026-09-17T08:00:00Z",
"overall_cognitive_load": "HIGH",
"load_score": 0.78,
"load_by_phase": {
"opening": 0.12,
"middle": 0.45,
"closing": 0.78
},
"peak_phase": "closing",
"overload_signals": [
{
"type": "repetition_request",
"evidence": "Sorry, could you say that again?",
"turn": 4,
"phase": "middle",
"weight": 0.30
},
{
"type": "confusion_phrase",
"evidence": "I still don't understand. What does that mean for me?",
"turn": 6,
"phase": "middle",
"weight": 0.25
},
{
"type": "jargon_density_spike",
"evidence": "sub-clause 4(b)(ii) of the agreement",
"turn": 3,
"phase": "middle",
"weight": 0.18
}
],
"interaction_dynamics": {
"turn_imbalance_score": 0.62,
"avg_silence_gap_ms": 2800,
"overlap_count": 0,
"participation_ratio": {"agent": 0.74, "callee": 0.26}
},
"script_patches": [
{
"original": "Under the terms of sub-clause 4(b)(ii) of the agreement",
"suggested": "According to our billing rules",
"rationale": "Legal jargon removed; Flesch-Kincaid grade reduced from 18 to 6"
}
],
"consent_validity_flag": "AT_RISK",
"consent_validity_reason": "Load score 0.78 exceeded threshold 0.65 during closing phase where commitment was recorded.",
"recommended_action": "SEND_WRITTEN_CONFIRMATION",
"false_positive_disclaimer": "Cognitive load inference is probabilistic. A flagged call does not constitute a legal finding. Human review is required before any adverse action.",
"flags": ["REQUIRES_HUMAN_REVIEW", "JARGON_DENSITY_HIGH"],
"analysis_mode": "heuristic",
"schema_version": "1.0"
}
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.
- 1mo ago First seen · 245 lines · 40 tokens per session scan A 16cb52264cfa
call-cognitive-load-monitor is a skill published in the GitHub repository CALLE-AI/awesome-phone-call-agents (109 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 2,250 once invoked, about $0.0002 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-19.
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…