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/wittyreference/twilio-claude-plugin/event-streamsnpx skills add wittyreference/twilio-claude-plugin --skill event-streamsgit clone --depth 1 https://github.com/wittyreference/twilio-claude-pluginWrote 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/wittyreference/twilio-claude-plugin/event-streams)<a href="https://agentmods.dev/skills/wittyreference/twilio-claude-plugin/event-streams"><img src="https://agentmods.dev/badge/skills/wittyreference/twilio-claude-plugin/event-streams.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.00012 | $0.04910 |
| Opus 5 | $0.00006 | $0.02455 |
| Sonnet 5 | $0.00002 | $0.00982 |
| Haiku 4.5 | $0.00001 | $0.00491 |
Grade A, and why
event-streams scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl "https://events.twilio.com/v1/Types?PageSize=20" \ How it starts
The opening of the file, as written. The whole thing — 370 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: event-streams description: Twilio Event Streams development guide. Use when building event-driven integrations, streaming Twilio events to webhooks/Kinesis/Segment, setting up sinks and subscriptions, or debugging event delivery.
Event Streams Development Skill
Guide for building event-driven integrations with Twilio Event Streams. Load this skill when streaming platform events (calls, messages, recordings, TaskRouter, etc.) to external systems via webhooks, AWS Kinesis, or Segment.
Evidence date: 2026-03-29 | Account: ACxx...xx
What Event Streams Cannot Do
Explicit list of things developers commonly assume work but don't:
- Cannot guarantee ordering — Events may arrive out of order. A
deliveredevent can arrive beforesent. Design consumers to be order-independent. - Cannot guarantee exactly-once delivery — At-least-once semantics. You WILL receive duplicates. Deduplicate using the
idfield (SID format varies by product:EZfor messaging,VWfor voice,NOfor error logs). - Cannot provide latency SLAs — Typical webhook delivery is 1-5 seconds, but no contractual guarantee. Voice Insights call summaries take 10-30 minutes.
- Cannot attach multiple subscriptions to one sink — Each sink supports exactly ONE subscription. Error: "Sink with SID DGxxx is in use". Create separate sinks for each subscription. [Evidence: DG1e0cf4..., 2026-03-29]
- Cannot subscribe to discontinued event types — API rejects with "Type is discontinued". Deprecated types ARE subscribable (they just won't fire for new activity). [Evidence: 2026-03-29]
- Cannot subscribe to
com.twilio.voice.twiml.requested— Listed in docs but API rejects: "Type not found in the system". [Evidence: 2026-03-29] - Cannot use the Node SDK
typesproperty —client.events.v1.typesisundefinedin the Twilio Node SDK. Use REST API directly for event type listing/fetching. [Evidence: 2026-03-29] - Cannot rely on
queuedevents for API-originated messages —com.twilio.messaging.message.queuedis subscribable but never fires for messages sent via the API. Onlysentanddeliveredarrive. [Evidence: SMaf53f7..., 2026-03-29] - Cannot use EventBridge as a native sink type — AWS EventBridge requires routing through a Segment sink as intermediary.
- Cannot receive transcript content via Event Streams — Use the Transcript API or status callbacks for actual transcript text.
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 · 370 lines · 12 tokens per session scan A 4ee5ddb2ab18
event-streams is a skill published in the GitHub repository wittyreference/twilio-claude-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 12 tokens to every session and 4,910 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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…