manage-calls-campaigns

manage-calls-campaigns is a skill for Claude Code from voicelogica/voice-logica-plugin. It costs 56 tokens per session (1,580 once invoked), scanned A, original, MIT.

A skill for reviewing Voice Logica call records, starting outbound calls or bulk campaigns, and running voice-agent test scenarios.

In plain words
What is it for?
Use it to inspect call and SIP logs, review transcripts and outcomes, start individual or bulk calls, manage scheduled calls, and run scenarios.
Why use it?
It helps investigate what happened during calls and organize outbound testing or campaigns using real call records.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the voice-logica plugin — 17 skills, 1 MCP server shipped together

Good fit Use it to inspect call and SIP logs, review transcripts and outcomes, start individual or bulk calls, manage scheduled calls, and run scenarios.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/voicelogica/voice-logica-plugin/manage-calls-campaigns
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 voicelogica/voice-logica-plugin --skill manage-calls-campaigns
Clone the repo
git clone --depth 1 https://github.com/voicelogica/voice-logica-plugin

Made for: Claude Code.

Or install voice-logica, the plugin that ships this one along with the rest of its 17 skills, 1 MCP server.

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 manage-calls-campaigns

README.md
[![agentmods](https://agentmods.dev/badge/skills/voicelogica/voice-logica-plugin/manage-calls-campaigns/github.svg)](https://agentmods.dev/skills/voicelogica/voice-logica-plugin/manage-calls-campaigns)
Your own site
<a href="https://agentmods.dev/skills/voicelogica/voice-logica-plugin/manage-calls-campaigns"><img src="https://agentmods.dev/badge/skills/voicelogica/voice-logica-plugin/manage-calls-campaigns/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 manage-calls-campaigns

Your own site · 80×15
<a href="https://agentmods.dev/skills/voicelogica/voice-logica-plugin/manage-calls-campaigns"><img src="https://agentmods.dev/badge/skills/voicelogica/voice-logica-plugin/manage-calls-campaigns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,580 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.00056 $0.01580
Opus 5 $0.00028 $0.00790
Sonnet 5 $0.00011 $0.00316
Haiku 4.5 $0.00006 $0.00158

Measured 12d ago against content hash 459d0a28d238, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

manage-calls-campaigns 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 12d 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.

skills/manage-calls-campaigns/SKILL.md · 106 lines

How it starts

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

Manage calls, campaigns, and scenarios

Use Call IDs. Do not invent them. Do not chase model or temperature first — those are usually platform defaults. Read the prompt, toolCalls, and call / SIP logs.

Call MCP tools

  • get_calls — list calls
  • get_calls_with_prompt — calls plus the prompt used
  • get_call_statistics — aggregates
  • get_call_logs — application / tool logs for a call
  • get_sip_logs — signaling
  • get_full_call — full call record
  • get_managed_agent_sessions — live / managed sessions
  • initiate_call — one outbound call
  • initiate_bulk_calls — campaign / bulk outbound
  • get_scheduled_calls / cancel_scheduled_calls

Default list window: last 7 days unless the user asked for another range. Summarize outcome, duration, and agent.

Recordings and history

  • Attended-transfer outbound legs may have a transcript but no full recording.
  • Very short / never-established calls may lack usable audio.
  • Calls that stay "open" may not finalize recording/transcript until hangup.
  • There is no archive feature. Use seen / unseen (auto when opened; Unseen only filter; shows who viewed and when).
  • Filters customers care about: unseen, date range, agent, direction, phone / Call ID.

If the call completed, a transcript exists, and audio should exist (not a transfer check-leg / not a 2-second hangup), file a ticket (create-support-ticket) with that Call ID. Do not invent an archive button.

Incomplete / cut-off audio: collect Call ID + timestamp in the recording (TTS cut, caller hangup, transfer mid-utterance, or network). Then diagnose from get_full_call / get_call_logs.

Scenario MCP tools

  • create_agent_scenario / list_agent_scenarios / get_agent_scenario
  • update_agent_scenario / delete_agent_scenario
  • generate_agent_scenarios
  • run_agent_scenario / run_agent_scenario_matrix / run_agent_scenario_suite
  • stop_agent_scenario_suite
  • get_agent_scenario_results
  • apply_scenario_improvements / dismiss_scenario_improvements

Read the full file on GitHub · 106 lines

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. 12d ago First seen · 106 lines · 56 tokens per session scan A 459d0a28d238

Subscribe to this mod's changes

manage-calls-campaigns is a skill published in the GitHub repository voicelogica/voice-logica-plugin (0 stars, last pushed 20d ago), licensed MIT. It adds 56 tokens to every session and 1,580 once invoked, about $0.0003 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-08-31.