Twilio for AI provides coding agents with skills and an MCP server for using Twilio services and documentation. The MCP server searches Twilio documentation and API specifications and retrieves full schemas for selected operations, while the skills supply procedural guidance to agents. Its catalogue add-ons are intended for Claude Code, Cursor, Codex, and other tools that support the Agent Skills standard.
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 twilio/ai --skill twilio-whatsapp-manage-sendersgit clone --depth 1 https://github.com/twilio/aiWrote 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/twilio/ai/twilio-whatsapp-manage-senders)<a href="https://agentmods.dev/skills/twilio/ai/twilio-whatsapp-manage-senders"><img src="https://agentmods.dev/badge/skills/twilio/ai/twilio-whatsapp-manage-senders/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/twilio/ai/twilio-whatsapp-manage-senders"><img src="https://agentmods.dev/badge/skills/twilio/ai/twilio-whatsapp-manage-senders.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00065 | $0.01470 |
| Opus 5 | $0.00032 | $0.00735 |
| Sonnet 5 | $0.00013 | $0.00294 |
| Haiku 4.5 | $0.00006 | $0.00147 |
Grade A, and why
twilio-whatsapp-manage-senders 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 13d 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
A WhatsApp sender is a phone number registered with WhatsApp Business through Twilio. Registration goes through a lifecycle of statuses before becoming ONLINE. Sandbox testing does not require a registered sender — see twilio-whatsapp-send-message.
Prerequisites
- Upgraded Twilio account (trial accounts cannot register production senders)
— See
twilio-account-setupfor signup and upgrade steps - A phone number capable of receiving SMS or voice verification
- Number must not already be registered with WhatsApp
- Environment variables:
TWILIO_ACCOUNT_SIDTWILIO_AUTH_TOKEN— Seetwilio-iam-auth-setupfor credential setup and best practices
- SDK:
pip install twilio/npm install twilio
Quickstart
Python
import os
from twilio.rest import Client
client = Client(os.environ["TWILIO_ACCOUNT_SID"], os.environ["TWILIO_AUTH_TOKEN"])
# Step 1: Initiate registration
sender = client.messaging.v2.channels.senders.create(
sender_id="whatsapp:+15017122661",
verification_method="sms"
)
print(sender.sid) # XExxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
print(sender.status) # CREATING
# Step 2: Submit the OTP Twilio sends to the number
sender = client.messaging.v2.channels.senders(sender.sid).update(
verification_code="123456"
)
print(sender.status) # ONLINE (may pass through TWILIO_REVIEW first)
Node.js
const twilio = require("twilio");
const client = twilio(process.env.TWILIO_ACCOUNT_SID, process.env.TWILIO_AUTH_TOKEN);
// Step 1: Initiate registration
const sender = await client.messaging.v2.channels.senders.create({
senderId: "whatsapp:+15017122661",
verificationMethod: "sms",
});
console.log(sender.sid, sender.status);
// Step 2: Submit the OTP
const verified = await client.messaging.v2.channels.senders(sender.sid).update({
verificationCode: "123456",
});
console.log(verified.status);
Sender Lifecycle Statuses
| Status | Meaning |
|---|---|
CREATING |
Registration initiated |
PENDING_VERIFICATION |
Awaiting OTP submission |
VERIFYING |
OTP being validated |
TWILIO_REVIEW |
Under Twilio/Meta review |
ONLINE |
Active and ready to send |
OFFLINE |
Inactive — check offlineReasons |
DRAFT |
Incomplete registration |
What ships with it
3 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.
- 13d ago First seen · 202 lines · 65 tokens per session scan A 0aacd6ecc0d8
twilio-whatsapp-manage-senders is a skill published in the GitHub repository twilio/ai (32 stars, last pushed 28d ago), licensed MIT. It adds 65 tokens to every session and 1,470 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-30.
Other skills, from other repositories
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
aws-sdk-java-v2-core
Provides AWS SDK for Java 2.x client configuration, credential resolution, HTTP client tuning, timeout, retry, and testing patterns. Use when creating or hardening AWS service clients, wiring Spring Boot beans, debugging auth or region issues, or choosing sync vs async SDK usage.
migrate-segw-to-rap
Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…