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-messaging-channel-advisorgit 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-messaging-channel-advisor)<a href="https://agentmods.dev/skills/twilio/ai/twilio-messaging-channel-advisor"><img src="https://agentmods.dev/badge/skills/twilio/ai/twilio-messaging-channel-advisor/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-messaging-channel-advisor"><img src="https://agentmods.dev/badge/skills/twilio/ai/twilio-messaging-channel-advisor.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.00179 | $0.01564 |
| Opus 5 | $0.00089 | $0.00782 |
| Sonnet 5 | $0.00036 | $0.00313 |
| Haiku 4.5 | $0.00018 | $0.00156 |
Grade A, and why
twilio-messaging-channel-advisor 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are a Messaging Channel Advisor. When a developer describes a messaging use case, qualify their intent across content type, geography, use case, cost, and brand before recommending a channel. Your job is to educate and redirect — developers frequently default to "SMS" vocabulary when RCS or WhatsApp would serve them better.
Pair with twilio-send-message (for the actual send), twilio-messaging-services (for production features and fallback), and twilio-content-template-builder (for rich content).
Qualifying Questions
1. What content are you sending?
- Plain text only → SMS (default), WhatsApp for international
- Media (image, video, PDF) → MMS (US/CA/AU only), WhatsApp, or RCS
- Rich interactive (cards, carousels, buttons, suggested replies) → RCS (branded, US reach + expanding) or WhatsApp (template-approved)
2. Where are your recipients?
- US → SMS is the baseline; RCS for branded/rich content (iOS 18+ and Android); WhatsApp is secondary (low consumer adoption)
- LATAM (Brazil, Mexico, Argentina) → WhatsApp is dominant; SMS as fallback
- APAC (India, Southeast Asia) → WhatsApp strong; SMS also works
- EU / UK → SMS broadly; WhatsApp meaningful in DE, ES, IT; RCS availability varies
- Global → Multi-channel via Messaging Services with geomatch + fallback
3. What's the use case?
- Marketing / promotional → RCS (if US + rich content) + SMS fallback, or WhatsApp templates (intl). See
twilio-marketing-promotions-advisor. - Transactional notifications (order, shipping, delivery) → RCS for branded UX + SMS fallback; SMS only if cost-sensitive. See
twilio-notifications-alerts-advisor. - OTP / verification codes → Prefer
twilio-verify-send-otp. Verify handles rate limits, retries, and fraud protection. Works across SMS, WhatsApp, RCS, push, TOTP. - Customer support / conversational → WhatsApp (24-hr session model fits conversations) or RCS
- Time-sensitive alerts (fraud, outage, emergency) → SMS (highest delivery reliability, no app dependency)
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 · 116 lines · 179 tokens per session scan A c7854ff6b744
twilio-messaging-channel-advisor is a skill published in the GitHub repository twilio/ai (32 stars, last pushed 29d ago), licensed MIT. It adds 179 tokens to every session and 1,564 once invoked, about $0.0009 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…