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 agentmods add skills/twilio/ai/twilio-debugging-observabilitynpx skills add twilio/ai --skill twilio-debugging-observabilitygit 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-debugging-observability)<a href="https://agentmods.dev/skills/twilio/ai/twilio-debugging-observability"><img src="https://agentmods.dev/badge/skills/twilio/ai/twilio-debugging-observability.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00082 | $0.03864 |
| Opus 5 | $0.00041 | $0.01932 |
| Sonnet 5 | $0.00016 | $0.00773 |
| Haiku 4.5 | $0.00008 | $0.00386 |
Grade B, and why
twilio-debugging-observability scanned grade B with 2 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 4d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
sink = requests.post( "https://events.twilio.com/v1/Sinks", Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
sink = requests.post( How it starts
The opening of the file, as written. The whole thing — 425 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Twilio provides several layers of debugging and observability: the Console Debugger for interactive troubleshooting, the Monitor REST API for programmatic alert queries, Event Streams for real-time error streaming, and status callbacks for per-resource delivery tracking. This skill covers the systematic approach to diagnosing issues and setting up production monitoring.
Prerequisites
- Twilio account with
TWILIO_ACCOUNT_SIDandTWILIO_AUTH_TOKEN-- seetwilio-iam-auth-setup - SDK:
pip install twilio requests/npm install twilio - For Event Streams: a publicly accessible HTTPS endpoint or AWS Kinesis stream
Quickstart
Check for recent errors on your account using the Monitor Alerts API.
Python
import os
from twilio.rest import Client
client = Client(os.environ["TWILIO_ACCOUNT_SID"], os.environ["TWILIO_AUTH_TOKEN"])
alerts = client.monitor.alerts.list(log_level="error", limit=10)
for alert in alerts:
print(f"{alert.date_created}: [{alert.error_code}] {alert.alert_text}")
Node.js
const twilio = require("twilio");
const client = twilio(process.env.TWILIO_ACCOUNT_SID, process.env.TWILIO_AUTH_TOKEN);
const alerts = await client.monitor.alerts.list({ logLevel: "error", limit: 10 });
alerts.forEach(a => {
console.log(`${a.dateCreated}: [${a.errorCode}] ${a.alertText}`);
});
Key Patterns
1. Systematic Debugging Workflow
When something fails, work through these layers in order:
1. Check status callbacks FIRST
(Did your endpoint receive delivery/call status? What error code?)
|
2. Check the resource directly via REST API
(GET /Messages/{sid} or /Calls/{sid} — current state + error_code)
|
3. Check number reputation / sender registration
(Is the number spam-flagged? Is A2P 10DLC registered? Toll-free verified?)
|
4. Check the Console Debugger for webhook/TwiML errors
(Console > Monitor > Errors — shows HTTP request/response details)
|
5. Check your webhook endpoint
(Is it reachable? Responding within 15s? Returning valid TwiML/200?)
|
6. Query Monitor Alerts API or Event Streams
(For patterns across many messages/calls, or historical analysis)
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.
- 4d ago First seen · 425 lines · 82 tokens per session scan B d952cadae46d
twilio-debugging-observability is a skill published in the GitHub repository twilio/ai (30 stars, last pushed 20d ago), licensed MIT. It adds 82 tokens to every session and 3,864 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…