manage-sms

manage-sms is a skill for Claude Code from voicelogica/voice-logica-plugin. It costs 48 tokens per session (878 once invoked), scanned A, original, MIT.

Instructions and tools for sending SMS text messages or Viber messages, managing sender IDs, and diagnosing delivery or character-encoding problems.

In plain words
What is it for?
Use it to add and verify senders, configure an agent’s SMS tool, send test messages, inspect delivery status, and troubleshoot Greek or UTF-8 text.
Why use it?
It separates common failures, such as an unverified sender from garbled text, and provides checks for each one.

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 add and verify senders, configure an agent’s SMS tool, send test messages, inspect delivery status, and troubleshoot Greek or UTF-8 text.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/voicelogica/voice-logica-plugin/manage-sms
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-sms
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-sms

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/voicelogica/voice-logica-plugin/manage-sms"><img src="https://agentmods.dev/badge/skills/voicelogica/voice-logica-plugin/manage-sms.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 878 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.00048 $0.00878
Opus 5 $0.00024 $0.00439
Sonnet 5 $0.00010 $0.00176
Haiku 4.5 $0.00005 $0.00088

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

Security

Grade A, and why

manage-sms 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 11d 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-sms/SKILL.md · 77 lines

How it starts

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

Manage Voice Logica SMS and Viber

MCP tools

  • send_sms
  • get_sms
  • list_sms_senders
  • add_sms_sender
  • verify_sms_sender
  • send_viber

Agent tool: send_sms on the agent (list_agent_tools / update_agent_tool) with a senderId.

Sender management in the app is admin or account-manager.

3-layer rule

  1. Add and verify a sender (add_sms_senderverify_sms_sender).
  2. Set senderId on the agent's send_sms tool.
  3. Test with a Call ID or a one-off send_sms, then get_sms. Always test to a real phone.

Never paste live sender tokens, provider passwords, or API keys into chat.

Phone numbers need a valid format (country code). Workflow sendSms nodes have the same requirement.

Not sending vs garbled UTF-8

These are different failures. Do not treat them as one.

Not sending (no message, provider error, pending verify):

  1. list_sms_senders — is the sender there and verified?
  2. Is senderId set on the agent tool?
  3. get_sms for the attempt — status and error.
  4. Check the Call ID toolCalls if this was during a call.
  5. If this is a workflow SMS: did execution reach the sendSms node? Any credit / balance issue?

Garbled UTF-8 (Greek or other non-ASCII looks like ???? or mojibake):

The sender and route are working. The payload encoding is wrong. Resend with proper UTF-8 text. Do not rotate the sender or rewrite the prompt as the first step. English-fine / Greek-broken is the signature.

Text the caller after a call

Two routes. Notification SMS (analysisSmsConfig / phoneNumbers / sendSmsCondition: "evaluate_condition") goes to the business, not the caller — wrong feature for this ask.

Route A — appointment was booked. Built-in confirmation on appointment settings: sendConfirmation, confirmationPrompt, confirmationSmsSenderId (manage-calendar-google-microsoft). Sender fallback: appointment setting → agent send_sms sender → VoiceLogica. Test a real call before promising it.

Read the full file on GitHub · 77 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. 11d ago First seen · 77 lines · 48 tokens per session scan A 077d000f91a7

Subscribe to this mod's changes

manage-sms is a skill published in the GitHub repository voicelogica/voice-logica-plugin (0 stars, last pushed 19d ago), licensed MIT. It adds 48 tokens to every session and 878 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-08-31.