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/agent-connectnpx skills add wittyreference/twilio-claude-plugin --skill agent-connectgit 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.00010 | $0.03457 |
| Opus 5 | $0.00005 | $0.01729 |
| Sonnet 5 | $0.00002 | $0.00691 |
| Haiku 4.5 | $0.00001 | $0.00346 |
Grade A, and why
agent-connect 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 3d 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.
4. **Verify ngrok tunnel before debugging**: A dead tunnel returns HTML 404 that mimics server 404. Verify: `curl -s -o /dev/null -w "%{http_code}" -X POST https://DOMAIN/health` must return 200. [conversations-invariant How it starts
The opening of the file, as written. The whole thing — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: agent-connect description: Twilio Agent Connect (TAC) SDK development guide. Use when building LLM-powered voice/SMS agents with automatic Customer Memory retrieval and Conversations Orchestrator integration. Do NOT use for direct Conversations layer API calls (use /customer-memory, /conversations-v2, /conversational-intelligence instead). allowed-tools: mcp__twilio__*, Read, Grep, Glob, Bash
Twilio Agent Connect (TAC)
SDK middleware that orchestrates voice (ConversationRelay) and SMS (Conversations API) channels with automatic Customer Memory retrieval and Intelligence analysis. You bring the LLM; TAC handles channel I/O, session management, memory retrieval, and conversation tracking.
Generally available — TypeScript (Node 20+) and Python (3.9+). Not PCI/HIPAA compliant.
Evidence: Assertion audit sourced from TAC documentation (2026-03-25) + live integration testing. See references/assertion-audit.md for provenance. Note: assertions are DOC-VERIFIED, not SID-backed. Live testing recommended for production decisions.
Scope
CAN
- Orchestrate voice calls via ConversationRelay WebSocket — STT/TTS handled by Twilio
- Orchestrate SMS via Conversations API webhooks — message routing automated
- Retrieve Customer Memory (observations, summaries, communications) per message/utterance
- Provide unified callback: same
handleMessageReady(userMessage, context, memoryResponse?)across channels - Create and manage conversations automatically via Conversations Orchestrator
- Write to Customer Memory via MemoryClient (observations, traits — added post-initial-docs)
- Handoff to human agents via
createHandoffTool()andonHandoffcallback - Support any LLM provider (OpenAI, Anthropic, Bedrock, LangChain)
- Active voice ingestion via
TWILIO_TAC_ENABLE_VOICE_ACTIVE_HYDRATION=true
CANNOT
- No custom STT/TTS — Uses ConversationRelay defaults; cannot specify Deepgram, ElevenLabs, etc. For custom providers, use ConversationRelay directly.
- No raw audio access — WebSocket is abstracted; only transcribed text exposed. Use Media Streams if you need audio.
- No ConversationRelay protocol events —
setup,interrupt,dtmfevents are not passed through to your callback. Only transcribed speech arrives. - No WhatsApp/Email/Chat channels — Only voice and SMS. For other channels, use the Conversations layer API directly (see Twilio Conversations documentation and the
/conversations-v2skill). - No MCP tools — TAC SDK is not wrapped in the MCP server. Interact via the SDK directly in your application code.
- No mid-conversation provider switch — Cannot change LLM or TTS mid-call through TAC.
- Voice memory auto-retrieval is broken —
TWILIO_TAC_ENABLE_VOICE_ACTIVE_HYDRATIONis documented but has a known bug where context returnsundefined. Use manual Recall via Customer Memory API at call setup instead.
What ships with it
2 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.
- 3d ago First seen · 259 lines · 10 tokens per session scan A 425ad681b4d8
agent-connect is a skill published in the GitHub repository wittyreference/twilio-claude-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 3,457 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…