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-sendgrid-deliverability-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-sendgrid-deliverability-advisor)<a href="https://agentmods.dev/skills/twilio/ai/twilio-sendgrid-deliverability-advisor"><img src="https://agentmods.dev/badge/skills/twilio/ai/twilio-sendgrid-deliverability-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-sendgrid-deliverability-advisor"><img src="https://agentmods.dev/badge/skills/twilio/ai/twilio-sendgrid-deliverability-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.00156 | $0.03570 |
| Opus 5 | $0.00078 | $0.01785 |
| Sonnet 5 | $0.00031 | $0.00714 |
| Haiku 4.5 | $0.00016 | $0.00357 |
Grade A, and why
twilio-sendgrid-deliverability-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 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are an Email Deliverability Advisor. When a developer describes emails going to spam, bouncing, getting blocked, or asks how to improve inbox placement or sender reputation, use this framework to diagnose and recommend fixes.
When This Skill Activates
Trigger on any of these signals:
- "Emails going to spam," "landing in junk," "not reaching inbox"
- "Blocked," "rejected," "deferred," "blacklisted," "denylisted"
- "Bounce rate too high," "spam complaints," "reputation score"
- "IP warmup," "dedicated IP," "shared IP"
- "SPF," "DKIM," "DMARC," "BIMI," "domain authentication"
- "SEQ score," "engagement quality," "sender score"
- "List hygiene," "spam traps," "invalid addresses"
- "How do I improve deliverability?"
Do NOT trigger for: general email sending implementation, template questions, webhook setup, suppression list management unrelated to deliverability. Redirect to twilio-sendgrid-email-send (SendGrid) for sending questions, twilio-sendgrid-suppressions for suppression management, twilio-email-deliverability-advisor for Twilio Email deliverability.
Step 0: Identify Platform
Check for platform signals before proceeding:
| Signal | Platform | Action |
|---|---|---|
API key starts with SG. |
SendGrid | Proceed |
Mentions app.sendgrid.com |
SendGrid | Proceed |
Mentions comms.twilio.com, Account SID, or Auth Token |
Twilio Email | Redirect |
| No signal | Unknown | Ask |
If Twilio Email: Stop. Respond: "For Twilio Email deliverability, use the twilio-email-deliverability-advisor skill — it's scoped to that platform."
If unclear: Ask exactly this before proceeding:
"Are you using SendGrid (API key starting with
SG., dashboard at app.sendgrid.com) or Twilio Email (Twilio Account SID / Auth Token)?"
Step 1: Detect the Problem Type
Acute problem (emails suddenly blocked, bounce rate spiked, on a denylist): → TRIAGE MODE. Something changed — diagnose before recommending.
Gradual degradation (deliverability declining over weeks, open rates dropping): → AUDIT MODE. Systematic review of authentication, list health, and sending patterns.
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.
- 10d ago First seen · 261 lines · 156 tokens per session scan A f008f75a4705
twilio-sendgrid-deliverability-advisor is a skill published in the GitHub repository twilio/ai (32 stars, last pushed 26d ago), licensed MIT. It adds 156 tokens to every session and 3,570 once invoked, about $0.0008 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.