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/brainstormnpx skills add wittyreference/twilio-claude-plugin --skill brainstormgit 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.00009 | $0.00867 |
| Opus 5 | $0.00005 | $0.00434 |
| Sonnet 5 | $0.00002 | $0.00173 |
| Haiku 4.5 | $0.00001 | $0.00087 |
Grade A, and why
brainstorm 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorming Your Twilio App
This is the starting point for building Twilio applications with AI agents.
How This Works
You describe your idea
↓
Claude Code helps you brainstorm (this template)
↓
Save output as concept.md for reference
↓
Claude Code enters plan mode, creates implementation plan
↓
You approve the plan
↓
Autonomous agents build it
(architect → spec → test-gen → dev → review → docs)
Available Twilio Capabilities
- Voice: Phone calls, IVR systems, call forwarding, conferencing, recordings
- Messaging: SMS, MMS, WhatsApp
- ConversationRelay: Real-time voice AI with LLM integration
- Verify: Phone number verification, 2FA, passwordless auth
- Sync: Real-time state synchronization across devices
- TaskRouter: Skills-based routing to workers and agents
Brainstorming Questions
Let's develop your idea step by step. I'll ask one question at a time:
-
Problem Statement: What problem are you trying to solve?
-
Target Users: Who will use this prototype?
-
Key Features: What are the must-have features?
-
Twilio Services: Which Twilio APIs would be most useful?
-
Integration Points: What external systems need to connect?
-
Success Criteria: How will you know if the prototype works?
- 6a. Products/Features Used: Which Twilio APIs does this concept use? (Voice, Messaging, Verify, Sync, TaskRouter, ConversationRelay, Intelligence, Serverless, etc.)
- 6b. Observable Success Evidence: What proves it worked? (e.g., "User receives SMS confirmation", "Call connects to agent within 30 seconds", "Transcript shows both parties spoke")
- 6c. Failure Indicators: What would indicate failure? (e.g., "User hears error message", "SMS never delivered", "Call drops after greeting")
- 6d. Validation Mapping: Based on products used, which validators apply?
Product Used Validators to Run Voice validateCall, validateRecording ConversationRelay validateConversationRelay, validateTwoWay Messaging validateMessage Verify validateVerification Sync validateSyncDocument TaskRouter validateTask Conference validateConference Intelligence validateTranscript, validateLanguageOperator Serverless validateServerlessFunctions (Always) validateDebugger
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 · 124 lines · 9 tokens per session scan A d21a304752d5
brainstorm is a skill published in the GitHub repository wittyreference/twilio-claude-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 867 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…