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/callbacksnpx skills add wittyreference/twilio-claude-plugin --skill callbacksgit clone --depth 1 https://github.com/wittyreference/twilio-claude-pluginWhat 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.00008 | $0.01683 |
| Opus 5 | $0.00004 | $0.00842 |
| Sonnet 5 | $0.00002 | $0.00337 |
| Haiku 4.5 | $0.00001 | $0.00168 |
Grade A, and why
callbacks 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 2d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Callbacks Functions
Service: prototype-core (CORE_BASE_URL). Deploy: ./scripts/deploy-services.sh dev
This directory contains Twilio Functions that handle status callbacks from various Twilio services. All callbacks are logged to Twilio Sync for deep validation during testing.
Purpose
These functions enable deep validation of Twilio API operations. Instead of just checking for a 200 OK from the API, we can verify:
- The actual status callbacks Twilio sends
- Whether errors occurred during processing
- The progression of status changes over time
Functions
| Function | Trigger | Purpose |
|---|---|---|
message-status.protected.js |
Message StatusCallback | Logs SMS/MMS delivery status |
call-status.protected.js |
Call StatusCallback | Logs voice call status changes |
task-status.protected.js |
TaskRouter EventCallback | Logs task and worker events |
verification-status.protected.js |
Verify webhook | Logs verification status |
fallback.protected.js |
Any FallbackUrl | Catches primary webhook failures |
pizza-order-status.protected.js |
RecordingStatusCallback | Triggers transcription, stores pizza order in Sync, sends SMS confirmation |
conference-health-monitor.protected.js |
Conference StatusCallback | Monitors conference participant events to detect orphaned participants (SUV-003) |
event-stream.js |
Event Streams webhook | Receives CloudEvents from Twilio Event Streams; stores in Sync List for inspection |
recording-test-status.protected.js |
RecordingStatusCallback | Captures full recording callback payloads to Sync for cross-method validation |
transcript-validation-status.protected.js |
Voice Intelligence webhook | Captures transcript completion and operator results to Sync for validation |
transcription-status.protected.js |
TranscriptionStatusCallback | Logs real-time transcription events (started, content, stopped, error) to Sync |
Sync Schema
All callbacks are logged to Sync Documents with the naming convention:
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.
- 2d ago First seen · 191 lines · 8 tokens per session scan A bce9c1de6c23
callbacks is a skill published in the GitHub repository wittyreference/twilio-claude-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 8 tokens to every session and 1,683 once invoked, about $0.0000 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-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…