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 voicelogica/voice-logica-plugin --skill manage-voice-agentsgit clone --depth 1 https://github.com/voicelogica/voice-logica-pluginWrote 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/voicelogica/voice-logica-plugin/manage-voice-agents)<a href="https://agentmods.dev/skills/voicelogica/voice-logica-plugin/manage-voice-agents"><img src="https://agentmods.dev/badge/skills/voicelogica/voice-logica-plugin/manage-voice-agents/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/voicelogica/voice-logica-plugin/manage-voice-agents"><img src="https://agentmods.dev/badge/skills/voicelogica/voice-logica-plugin/manage-voice-agents.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.00059 | $0.00613 |
| Opus 5 | $0.00030 | $0.00307 |
| Sonnet 5 | $0.00012 | $0.00123 |
| Haiku 4.5 | $0.00006 | $0.00061 |
Grade A, and why
manage-voice-agents 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.
How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage Voice Logica agents
Use the Voice Logica MCP. Do not invent agent IDs, phone numbers, or API fields.
Before anything else
- Confirm the MCP is connected. If tools fail because MCP is not connected, tell the user to Connect Voice Logica MCP (OAuth to https://app.voicelogica.ai). Use an API key only if the client has no Connect flow.
- List current agents first when the user names an agent. Match by name, then use the real ID.
- Open the specialist skill for the job. Do not do a deep edit, diagnosis, or integration change from this router.
Route to the right skill
- Create / build / go-live a new agent:
edit-voice-agents - Edit settings, prompts, languages, transfers, knowledge:
edit-voice-agents - Prompt over ~20k / knowledge files / router+specialist:
edit-voice-agents - Call went badly / change how the agent behaves:
fix-agent-behavior - Diagnose a failed call, missing tool, or "is it the model?":
troubleshoot-voice-agents - DIDs, SIP phones, inbound numbers, edge devices, registration, one-way audio:
manage-phones - Connect any integration (OAuth, API, tunnels, edge):
manage-integrations - HubSpot / Zoho / Salesforce:
manage-crm - Woo, Shopify, and other shops:
manage-ecommerce - Soft1, Galaxy, Pylon, Entersoft:
manage-erp - Google / Microsoft calendar, contacts, Chat:
manage-calendar-google-microsoft - SMS / Viber senders:
manage-sms - Freshdesk, Zendesk, Jira, couriers, payments:
manage-helpdesk-ops - Workflows, triggers, nodes:
manage-workflows - Call logs, outbound campaigns, test scenarios:
manage-calls-campaigns - Companies, plans, operating hours:
manage-company-billing - File a ticket in the Voice Logica app (Contact Support) with Call IDs:
create-support-ticket— portal fallback https://support.voicelogica.ai - Full MCP tool catalog:
use-voice-logica-mcp
Transfers live on the agent (Transfer Connection + transfer prompt). Phone registrations live in manage-phones. Do not mix them. Attended / warm often fails on PBXs that decline SIP REFER — edit-voice-agents picks blind vs attended.
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.
- 12d ago First seen · 42 lines · 59 tokens per session scan A 005581a9874e
manage-voice-agents is a skill published in the GitHub repository voicelogica/voice-logica-plugin (0 stars, last pushed 20d ago), licensed MIT. It adds 59 tokens to every session and 613 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.
Other skills, from other repositories
gws-gmail-send
Skill "gws-gmail-send" from googleworkspace/cli, covering gmail +send, usage, flags, examples and tips.
gws-gmail
Gmail: Send, read, and manage email.
gws-shared
The gws binary must be on $PATH. See the project README for install options.
gws-sheets
Google Sheets: Read and write spreadsheets.
gws-modelarmor
Google Model Armor: Filter user-generated content for safety.
gws-docs
Read and write Google Docs.