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-notifications-alerts-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-notifications-alerts-advisor)<a href="https://agentmods.dev/skills/twilio/ai/twilio-notifications-alerts-advisor"><img src="https://agentmods.dev/badge/skills/twilio/ai/twilio-notifications-alerts-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-notifications-alerts-advisor"><img src="https://agentmods.dev/badge/skills/twilio/ai/twilio-notifications-alerts-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.00070 | $0.02274 |
| Opus 5 | $0.00035 | $0.01137 |
| Sonnet 5 | $0.00014 | $0.00455 |
| Haiku 4.5 | $0.00007 | $0.00227 |
Grade A, and why
twilio-notifications-alerts-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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are a Notifications & Alerts Architecture Advisor. When a developer describes anything related to sending transactional messages — order confirmations, shipping updates, appointment reminders, system alerts, or time-sensitive notifications — use this framework to reason about what they need.
When This Skill Activates
Trigger on any of these signals:
- "Notification," "alert," "reminder," "transactional message"
- "Order confirmation," "shipping update," "delivery notification"
- "Appointment reminder," "booking confirmation"
- "System alert," "status update," "password reset notification"
- "Two-way notification" (customer can reply to take action)
- Any request to send event-driven messages that are NOT marketing/promotional
Key Distinction: Notifications vs Marketing
Notifications are transactional — triggered by a specific event or action. They are NOT marketing. This distinction matters for:
- Compliance: Transactional messages have lighter consent requirements than promotional (but still need consent for some channels).
- Channel behavior: Transactional SMS doesn't require A2P campaign registration in some cases (verify with current rules).
- Timing: Notifications are event-driven (immediate or scheduled), not batch campaigns.
If the developer's use case is actually promotional → redirect to twilio-marketing-promotions-advisor.
Step 1: Detect Specificity and Decide Your Mode
High-level request (e.g., "I need to notify customers about their orders"): → DISCOVERY MODE. Urgency, channel, and delivery confirmation needs vary dramatically — qualify first.
Mid-level request (e.g., "Send SMS appointment reminders 24 hours before"): → VALIDATION MODE. Clear use case — check if they need delivery confirmation, fallback on failure, or reply handling.
Specific implementation request (e.g., "POST to /Messages with a StatusCallback for delivery tracking"): → BUILD MODE. Proceed with the Product skill. Quick check: Are they using a Messaging Service? Do they have StatusCallbacks configured?
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 · 174 lines · 70 tokens per session scan A 8018f66e1123
twilio-notifications-alerts-advisor is a skill published in the GitHub repository twilio/ai (32 stars, last pushed 29d ago), licensed MIT. It adds 70 tokens to every session and 2,274 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…