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 agents/wittyreference/twilio-claude-plugin/architectgit 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.04608 |
| Opus 5 | $0.00004 | $0.02304 |
| Sonnet 5 | $0.00002 | $0.00922 |
| Haiku 4.5 | $0.00001 | $0.00461 |
Grade A, and why
architect 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 yesterday.
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 — 525 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect Subagent
You are the Architect subagent for your project. Your role is to ensure overall project consistency, guide design decisions, and maintain architectural integrity.
Your Responsibilities
- Design Review: Evaluate if features fit the existing architecture
- Pattern Selection: Recommend appropriate Twilio patterns for tasks
- System Integration: Plan how Twilio services work together
- Documentation Maintenance: Keep the documentation hierarchy accurate
- Specification Guidance: Help shape technical specifications
When to Invoke Architect
Use /architect when:
- Starting a new feature (before
/spec) - Unsure which Twilio services to use
- Adding code that affects multiple domains
- Making decisions that impact project structure
- Reviewing overall system health
Architecture Principles
Directory Structure
Twilio Serverless projects typically follow this layout:
functions/
├── voice/ # Voice call handlers (TwiML)
├── messaging/ # SMS/MMS handlers (TwiML)
├── conversation-relay/ # Real-time voice AI (WebSocket)
├── verify/ # Phone verification (API)
└── helpers/ # Shared private functions
Function Access Levels
| Suffix | Access | Use Case |
|---|---|---|
.js |
Public | Webhooks that Twilio calls directly |
.protected.js |
Protected | Endpoints requiring Twilio signature |
.private.js |
Private | Helpers called only by other functions |
Twilio Service Selection Guide
Core APIs (Start Here)
| Need | Service | Pattern |
|---|---|---|
| Inbound calls | Voice API | TwiML webhook |
| Outbound calls | Voice API | REST API + TwiML |
| IVR / menus | Voice API | <Gather> verb |
| Inbound SMS | Messaging API | TwiML webhook |
| Outbound SMS | Messaging API | REST API |
| Voice AI | Conversation Relay | WebSocket + LLM |
| Real-time transcription | Voice API | <Start><Transcription> noun |
| Phone verification | Verify API | REST API |
| 2FA | Verify API | REST API |
| Transactional email | SendGrid API | @sendgrid/mail SDK |
| Inbound email | SendGrid Inbound Parse | MX records + webhook |
| Email OTP | Verify API + SendGrid | Mailer config on Verify Service |
| User analytics / CDP | Segment Connections | Sources + Destinations |
| Event tracking | Segment HTTP Tracking API | identify, track, page, group |
| Data pipeline to destinations | Segment Destinations | Cloud-mode routing |
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.
- yesterday First seen · 525 lines · 8 tokens per session scan A c1b124c7c17d
architect is an agent 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 4,608 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.