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 znak-callopsgit 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/znak-callops)<a href="https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/znak-callops"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/znak-callops/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/znak-callops"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/znak-callops.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.00046 | $0.00976 |
| Opus 5.5 | $0.00018 | $0.00390 |
| Sonnet 5.5 | $0.00009 | $0.00195 |
| Haiku 4.5 | $0.00005 | $0.00098 |
Grade A, and why
znak-callops 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ZNAK CallOps
Turn a bounded service inquiry into a CALL-E plan and an inspectable result. This skill adds a small executable evidence checker: a completed call is not a verified answer, and a quote present in a transcript is not independent proof of its truth.
Setup and verification
Requires Python 3.10+ for the local helper, and an Agent Skills-compatible host
with authenticated CALL-E MCP tools or Python 3.11+ with the optional official SDK
adapter for live calls. Copy this whole directory to
the host's skill directory. For Codex, use ~/.codex/skills/znak-callops/.
Use references/call-e.md to connect the official provider.
The helper uses only Python's standard library and never connects to a network.
From the repository root, run the synthetic no-call demonstration:
python3 skills/znak-callops/scripts/callops.py demo
python3 -m unittest discover -s skills/znak-callops/scripts -p 'test_*.py'
Read references/examples.md for inputs, expected results,
and manual verification. These tests exercise local code, not the CALL-E service.
The live host integration has not been verified by a real call in this contribution.
For the optional executable SDK path, read
references/sdk-dispatch.md. dispatch.py defaults to
a no-network preview and imports the official SDK only after explicit live/read
opt-in. No live CALL-E call has been verified through either path.
Workflow
- Establish the user's exact question, service scope, preferred time window, known destination, language, and permission to call that recipient for this purpose. Read references/safety.md before dispatch.
- Use
prepare-goalwith the resolved request to produce the bounded call brief. Show the masked destination, purpose, and inquiry only; do not book, accept a quote, pay, cancel, or disclose additional personal details. A request to prepare a plan alone does not authorize a phone call. - Invoke CALL-E
plan_callwith the user's latest message verbatim inuser_input. Pass only known fields; use the prepared brief asgoal. Follow the live tool schema. A plan does not place a call. - After the user clearly authorizes this call and the plan is ready, invoke
run_callonce with exactly the returnedplan_idandconfirm_token. Keep those opaque values out of public artifacts. Retain the returnedrun_idin the host's private task record. Follow the recovery rules in the provider reference; a timeout is not permission to redial. - Read
get_call_rununtil a terminal outcome or a monitoring pause. If transcript turns are available, preserve their exact text, order, and speaker. Map them to the helper's documented input. The provider's response schema is discovered at runtime; this normalized packet is local, not a CALL-E wire format. - Propose full provider-turn quotations for
availability,quoted_price, andfollow_up. Never clip qualifying words. Runvalidate-resulton that packet. If the provider exposes only a summary, leave the unsupported fields UNKNOWN. - Return the checked quotes and their source pointers. Review relevance and ambiguity: the checker verifies quote identity, not semantic interpretation, speaker authenticity, provider honesty, or that a time remains available. Leave booking and other commitments to a separate user decision.
What ships with it
12 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.
- assets/synthetic_inquiry.json 1.5 KB
- assets/synthetic_missing_price.json 914 B
- assets/synthetic_request.json 157 B
- references/call-e.md 2.8 KB
- references/examples.md 3.4 KB
- references/safety.md 2.6 KB
- references/sdk-dispatch.md 3.9 KB
- scripts/callops.py 8.8 KB runs code
- scripts/dispatch.py 8.7 KB runs code
- scripts/requirements-live.txt 16 B
- scripts/test_callops.py 4.8 KB runs code
- scripts/test_dispatch.py 5.9 KB runs code
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 · 78 lines · 46 tokens per session scan A 7458baae3a46
znak-callops is a skill published in the GitHub repository CALLE-AI/awesome-phone-call-agents (109 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 976 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-15.
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…