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/branded-callingnpx skills add wittyreference/twilio-claude-plugin --skill branded-callinggit clone --depth 1 https://github.com/wittyreference/twilio-claude-pluginWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/wittyreference/twilio-claude-plugin/branded-calling)<a href="https://agentmods.dev/skills/wittyreference/twilio-claude-plugin/branded-calling"><img src="https://agentmods.dev/badge/skills/wittyreference/twilio-claude-plugin/branded-calling.svg" alt="Measured on agentmods" height="20"></a>What 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.00013 | $0.05755 |
| Opus 5 | $0.00006 | $0.02877 |
| Sonnet 5 | $0.00003 | $0.01151 |
| Haiku 4.5 | $0.00001 | $0.00575 |
Grade A, and why
branded-calling 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.
See [references/reports-api-guide.md](references/reports-api-guide.md) for complete API patterns, curl examples, and a monthly health check script. How it starts
The opening of the file, as written. The whole thing — 416 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: branded-calling description: Twilio Branded Calling development guide. Use when improving outbound call answer rates, displaying business name/logo on caller ID, setting up SHAKEN/STIR attestation, remediating spam labels, or configuring CNAM. allowed-tools: mcp__twilio__*, Read, Grep, Glob
Branded Calling Skill
Decision-making guide for the Twilio call trust stack: Branded Calling (Basic and Enhanced), SHAKEN/STIR attestation, Voice Integrity spam remediation, and CNAM caller ID. Load this skill when a developer wants to improve outbound call answer rates, display a business name or logo on the recipient's phone, remediate spam/scam labels, or configure caller identity.
Evidence date: 2026-03-28 | Account: ACxx...xx | Trust Hub policies verified via live API
Scope
What the Call Trust Stack CAN Do
- Display a business name on the recipient's phone (Basic Branded Calling — T-Mobile, some carriers)
- Display a business name + logo + call reason on the recipient's phone (Enhanced Branded Calling — T-Mobile, limited Apple/iOS)
- Achieve SHAKEN/STIR A-level attestation on outbound calls (proves your business owns the calling number)
- Remediate spam/scam labels on your numbers across T-Mobile, AT&T, Verizon via Voice Integrity
- Register CNAM (Caller Name) for display on landlines and some carriers
- Track branded call delivery via Voice Insights (branded call status, SHAKEN/STIR verification)
- Manage the full setup programmatically via Trust Hub API (TrustProducts, CustomerProfiles, EndUsers, Documents)
What the Call Trust Stack CANNOT Do
- Cannot guarantee display on every device — Branded Calling display depends on the recipient's carrier, device, and OS. Not all combinations show the brand. There is no way to force display.
- Cannot brand inbound calls — Branded Calling applies to outbound calls only. Inbound caller ID is controlled by the originating carrier.
- Cannot use Branded Calling without Voice Integrity (Enhanced) — Enhanced Branded Calling requires an approved Voice Integrity trust product as a prerequisite.
- Cannot skip the LOA (Letter of Authorization) — Both Basic and Enhanced require a signed LOA proving your business is authorized to use the phone numbers.
- Cannot change the display name per call — The display name is registered at the Trust Product level. All calls from assigned numbers show the same name.
- Cannot use toll-free numbers — Branded Calling is for local and mobile numbers only. Toll-free has its own trust framework.
- Cannot self-approve — All Branded Calling trust products require Twilio review and carrier-side registration. Approval timelines are measured in business days to weeks.
- Cannot use Branded Calling outside the US — Currently US-only for both Basic and Enhanced tiers.
- Cannot add a logo without Enhanced tier — Basic shows business name only. Logo requires Enhanced Branded Calling.
- Cannot brand calls made via SIP Trunking — Branded Calling requires calls to originate from the Twilio Programmable Voice platform (API or TwiML). SIP trunk calls bypass the branding layer.
What ships with it
5 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 · 416 lines · 13 tokens per session scan A 1a656c6e2889
branded-calling is a skill published in the GitHub repository wittyreference/twilio-claude-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 5,755 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…