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/twilio-logsgit 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/commands/wittyreference/twilio-claude-plugin/twilio-logs)<a href="https://agentmods.dev/commands/wittyreference/twilio-claude-plugin/twilio-logs"><img src="https://agentmods.dev/badge/commands/wittyreference/twilio-claude-plugin/twilio-logs.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.00026 | $0.00702 |
| Opus 5 | $0.00013 | $0.00351 |
| Sonnet 5 | $0.00005 | $0.00140 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
twilio-logs 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 4d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Twilio Logs Analyzer
Fetch and analyze Twilio debugger logs to identify issues. Uses MCP tools for structured, SID-targeted analysis.
Strategy: SID-First
Always start with the most targeted tool available:
Have a specific resource SID?
Use the domain-specific validation tool for deep analysis:
| Resource | Tool | What You Get |
|---|---|---|
Call (CA...) |
validate_call(callSid) |
Status + notifications + Voice Insights + recordings |
Message (SM...) |
validate_message(messageSid) |
Delivery status + debugger alerts |
Recording (RE...) |
validate_recording(recordingSid) |
Completion status + duration |
Transcript (GT...) |
validate_transcript(transcriptSid) |
Completion + sentences |
| Any resource SID | validate_debugger(resourceSid: "XX...") |
Debugger alerts filtered to that resource |
Investigating a time window?
get_debugger_logs(limit, startDate, endDate)— list alerts in a windowanalyze_errors— automatic pattern detection and error grouping
General health check?
validate_debugger(lookbackSeconds: 300)— recent alerts across the account
CLI fallback (human debugging only)
twilio debugger:logs:list --limit 20
twilio debugger:logs:list --limit 50 --start-date "YYYY-MM-DD"
Use CLI only for interactive human debugging sessions, not agent workflows.
Analysis Focus
Error Categories
- Authentication Errors: Invalid credentials, expired tokens
- Webhook Failures: Unreachable URLs, timeouts, invalid TwiML
- Rate Limiting: Too many requests
- Invalid Parameters: Malformed phone numbers, missing required fields
- Account Issues: Insufficient funds, suspended numbers
For Each Error Found
Provide:
- Timestamp: When the error occurred
- Error Code: Twilio error code
- Error Message: Description of the error
- Resource: What was being accessed (call, message, etc.)
- Likely Cause: What probably caused this
- Suggested Fix: How to resolve it
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.
- 4d ago First seen · 96 lines · 26 tokens per session scan A f833f7a73c98
twilio-logs is a command published in the GitHub repository wittyreference/twilio-claude-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 26 tokens to every session and 702 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
git
Git operations with intelligent commit messages and workflow optimization.
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.