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 commands/wittyreference/twilio-claude-plugin/deploygit 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.00025 | $0.00616 |
| Opus 5 | $0.00013 | $0.00308 |
| Sonnet 5 | $0.00005 | $0.00123 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
deploy 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment Helper
Deploy Twilio serverless functions across 3 services (core, ai, labs) via scripts/deploy-services.sh.
Pre-Deployment Checklist
Before deploying, verify:
-
All Tests Pass
npm test npm run test:e2e -
Linting Passes
npm run lint -
CLI Profile — Verify active profile matches target account:
twilio profiles:list -
No Uncommitted Changes
git status
Deployment Commands
Deploy All Services (Recommended)
./scripts/deploy-services.sh dev # Deploy core + ai + labs to dev
./scripts/deploy-services.sh prod # Deploy to production
Deploy Single Service
./scripts/deploy-services.sh --only core dev
./scripts/deploy-services.sh --only ai dev
./scripts/deploy-services.sh --only labs dev
Deploy Ephemeral Validation Service
./scripts/deploy-services.sh --only validation dev # Deploy fresh
./scripts/deploy-services.sh --teardown validation # Remove after testing
Service Architecture
| Service | Directories | Env Var |
|---|---|---|
prototype-core |
voice, callbacks, helpers, messaging, messaging-services, taskrouter, verify, phone-numbers, proxy, sync, video | CORE_BASE_URL |
prototype-ai |
conversation-relay, webinar, helpers | AI_BASE_URL |
prototype-labs |
pay, sip, helpers | LABS_BASE_URL |
prototype-validation |
conversation-relay, callbacks, helpers, messaging (ephemeral) | VALIDATION_BASE_URL |
Manifest: services.json
Post-Deployment
- Update
.envwith domains from deploy output (CORE_BASE_URL, AI_BASE_URL, LABS_BASE_URL) - Wire phone numbers: Configure voice/messaging webhooks on your Twilio phone numbers via Console or CLI (see DESIGN_DECISIONS.md D45)
- Verify endpoints — make test calls using MCP
make_call/send_sms, validate withvalidate_call(callSid) - Check debugger:
validate_debugger(lookbackSeconds: 300)
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 · 87 lines · 25 tokens per session scan A 76048dbd6428
deploy is a command published in the GitHub repository wittyreference/twilio-claude-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 616 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.