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/lookupnpx skills add wittyreference/twilio-claude-plugin --skill lookupgit 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/lookup)<a href="https://agentmods.dev/skills/wittyreference/twilio-claude-plugin/lookup"><img src="https://agentmods.dev/badge/skills/wittyreference/twilio-claude-plugin/lookup.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.00008 | $0.04069 |
| Opus 5 | $0.00004 | $0.02034 |
| Sonnet 5 | $0.00002 | $0.00814 |
| Haiku 4.5 | $0.00001 | $0.00407 |
Grade A, and why
lookup 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 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.
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 — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: lookup description: Twilio Lookup v2 phone number intelligence guide. Use when validating phone numbers, detecting line type or carrier, checking fraud risk (SIM swap, SMS pumping), verifying caller identity, or choosing between Lookup data packages. allowed-tools: mcp__twilio__lookup_phone_number, mcp__twilio__check_fraud_risk, Read, Grep, Glob
Lookup v2 Development Skill
Decision-making guide for Twilio Lookup v2 — phone number intelligence, validation, fraud detection, and identity verification. Load this skill when choosing which data packages to use, interpreting Lookup responses, or integrating number intelligence into voice/messaging workflows.
Evidence date: 2026-03-29 | Account: ACxx...xx
Scope
What Lookup v2 Can Do
- Validate phone numbers (free) — format check, E.164 normalization, country detection
- Identify line type — 12-type classification including fixedVoip vs nonFixedVoip distinction
- Retrieve carrier data — carrier name, MCC, MNC for mobile/VoIP numbers
- CNAM lookup — caller name and type (US numbers only)
- Detect SIM swap — carrier-reported SIM change history (Beta, 10 countries)
- Assess SMS pumping risk — per-number risk score and carrier risk category
- Check number reassignment — whether a US number changed owners since a given date
- Verify identity — match name/address/DOB against carrier records (10 countries)
- Check line status — HLR-based reachability (active/reachable/unreachable/inactive)
- Detect call forwarding — unconditional forwarding status (UK only, Private Beta)
- Combine multiple packages in a single API call — comma-separated
fieldsparameter - Override line type classification — persist per-account line type override for a number
What Lookup v2 Cannot Do
- Cannot look up information by name/address — input is always a phone number; you cannot reverse-search "who owns this number" without a number
- Cannot get CNAM for non-US numbers — returns error 60600 (out of coverage); no international CNAM
- Cannot detect conditional call forwarding — only unconditional forwarding is detected, and only for UK carriers
- Cannot guarantee SIM swap data without carrier registration — returns error 60606 until carrier approval is completed
- Cannot use Reassigned Number outside the US — US-only dataset with monthly update cadence
- Cannot get real-time SMS pumping scores — scores are statistical models, not live traffic analysis; they change between calls but reflect aggregate patterns
- Cannot write data — Lookup v2 is read-only (GET only). The one exception is Line Type Override (POST/DELETE)
- Cannot batch multiple phone numbers in one request — one number per API call; use concurrent requests for bulk lookups
- Cannot avoid billing on CNAM requests that return no data — billed per request regardless of whether caller name is found
- Cannot use Phone Number Quality Score or Pre-fill without account provisioning — returns 60606; contact Twilio sales
What ships with it
3 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 · 305 lines · 8 tokens per session scan A 4132dac2494e
lookup is a skill 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,069 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…