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 veyra-campaign-plannergit 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/veyra-campaign-planner)<a href="https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/veyra-campaign-planner"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/veyra-campaign-planner/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/veyra-campaign-planner"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/veyra-campaign-planner.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.00041 | $0.00774 |
| Opus 5 | $0.00020 | $0.00387 |
| Sonnet 5 | $0.00008 | $0.00155 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
veyra-campaign-planner 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 today.
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.
Veyra Campaign Planner
Use this skill when a user wants to turn a business calling process into a reusable Veyra workflow and campaign. Produce an actionable campaign brief, help the user review Veyra's generated graph and compiled CALL-E request, and preserve a hard boundary between planning and placing real calls.
This skill does not place calls. Veyra's runnable implementation is in apps/web/veyra/; read its README only when setup, execution, or deployment is requested.
Prepare The Campaign Brief
Gather only information that changes the workflow:
- caller identity and organization
- specific purpose and desired outcome
- recipient source and evidence that contact is authorized
- information to collect, qualification rules, and allowed next steps
- required disclosures, prohibited claims, opt-out behavior, and voicemail behavior
- locale and recipient-local calling window when known independently of the phone number
If a missing detail affects authorization, safety, or a real-world commitment, stop and ask for it. Otherwise state a conservative assumption.
Return:
- A concise workflow name.
- One plain-English Veyra prompt describing the goal, conversation stages, branches, fields to capture, qualification criteria, next steps, and restrictions. Describe intent rather than fixed speech so CALL-E can converse naturally.
- A short review checklist covering consent, terminal branches, captured fields, qualification logic, and prohibited actions.
Do not invent contacts, phone numbers, consent, company policy, offers, appointment availability, or facts the caller has not supplied.
Review The Generated Workflow
After Veyra generates or edits the graph, verify:
- exactly one start and at least one terminal path
- AI identity, organization, purpose, and permission occur before substantive questions
- refusal, opt-out, wrong-person, and do-not-contact paths end without persuasion
- every decision edge is understandable and every captured field is used or returned
- qualification rules reference fields actually collected
- next steps are bounded and do not promise unavailable transfers, bookings, prices, approvals, or callbacks
- the compiled CALL-E task preserves intent without forcing a monotonous verbatim script
- the result schema distinguishes negative answers from unknown, unavailable, or unestablished outcomes
What ships with it
2 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.
- today First seen · 78 lines · 41 tokens per session scan A 9f2a15671da6
veyra-campaign-planner is a skill published in the GitHub repository CALLE-AI/awesome-phone-call-agents (88 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 774 once invoked, about $0.0002 per session on Opus 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-12.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…