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 create-support-ticketgit 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/create-support-ticket)<a href="https://agentmods.dev/skills/voicelogica/voice-logica-plugin/create-support-ticket"><img src="https://agentmods.dev/badge/skills/voicelogica/voice-logica-plugin/create-support-ticket/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/create-support-ticket"><img src="https://agentmods.dev/badge/skills/voicelogica/voice-logica-plugin/create-support-ticket.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.00053 | $0.00570 |
| Opus 5 | $0.00026 | $0.00285 |
| Sonnet 5 | $0.00011 | $0.00114 |
| Haiku 4.5 | $0.00005 | $0.00057 |
Grade A, and why
create-support-ticket 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 10d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a Voice Logica support ticket
File it in the Voice Logica app (Contact Support) through MCP. These are not Freshdesk / Zendesk tickets (manage-helpdesk-ops) and not mailbox email.
Confirm the MCP is connected (Connect / OAuth to https://app.voicelogica.ai). Use an API key only if the client has no Connect flow.
When to file
- The user asks to open a ticket, escalate, or get a human.
- After one honest diagnosis pass the issue is still broken, or it needs a human (carrier, number porting, billing, account access).
- SIP REFER declined, a recording that should exist is missing, or the agent spoke JSON / tool names / brackets.
Do not file a ticket for a setting change you can do in this chat.
Required fields
Collect before creating. Do not invent Call IDs.
- Short subject (what failed — not "help")
- Expected vs actual
- Agent name and ID
- Call ID(s) if it is a call, transfer, or recording issue
- When it started / whether it used to work
- What you already tried
Also useful when relevant: destination type (mobile / landline / extension), whether the destination rang, DID / public number, and whether the window had zero Call IDs (traffic never reached Voice Logica).
Write the body in the user language. Put IDs in as plain text.
MCP tools (do not invent others)
create_ticketlist_tickets/get_ticketlist_ticket_mentions/reply_to_ticket/change_ticket_statusclose_all_tickets— admin only; do not use unless the user asked
How to create
list_ticketsfirst. If an open ticket already covers this,reply_to_ticketinstead of a duplicate.create_ticketwith the subject and body above. Always include Call IDs and agent IDs in the body when you have them.- Return the ticket ID and a one-line summary of what you filed.
- If create fails or no ticket tool is available, say so and give the Support portal: https://support.voicelogica.ai — tell them to file there with the same Call IDs.
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.
- 10d ago First seen · 52 lines · 53 tokens per session scan A af9d80a44976
create-support-ticket is a skill published in the GitHub repository voicelogica/voice-logica-plugin (0 stars, last pushed 18d ago), licensed MIT. It adds 53 tokens to every session and 570 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-shared
The gws binary must be on $PATH. See the project README for install options.
gws-sheets
Google Sheets: Read and write spreadsheets.
gws-gmail
Gmail: Send, read, and manage email.
gws-modelarmor
Google Model Armor: Filter user-generated content for safety.
gws-docs
Read and write Google Docs.