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/env-doctornpx skills add wittyreference/twilio-claude-plugin --skill env-doctorgit 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/env-doctor)<a href="https://agentmods.dev/skills/wittyreference/twilio-claude-plugin/env-doctor"><img src="https://agentmods.dev/badge/skills/wittyreference/twilio-claude-plugin/env-doctor.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.00012 | $0.00600 |
| Opus 5 | $0.00006 | $0.00300 |
| Sonnet 5 | $0.00002 | $0.00120 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
env-doctor 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 5d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: env-doctor description: Diagnose shell and .env credential conflicts. Use when hitting 401 errors, auth failures after switching Twilio accounts, or mysterious environment variable issues.
Environment Doctor
Diagnose shell vs .env conflicts that cause mysterious Twilio auth failures. Run this when:
- A new user clones the repo and gets 401 errors
- API calls fail after switching between Twilio accounts or projects
- Regional routing errors appear unexpectedly
- MCP tools return auth failures but CLI works (or vice versa)
Usage
Run the diagnostic script:
./scripts/env-doctor.sh
What It Checks
| Check | What It Detects |
|---|---|
| 1. Project .env | Missing .env file |
| 2. Credential conflicts | TWILIO_ACCOUNT_SID, TWILIO_AUTH_TOKEN, TWILIO_PHONE_NUMBER mismatch between shell env and .env file |
| 3. Regional routing | Orphaned TWILIO_REGION/TWILIO_EDGE in shell that silently redirect all API calls to regional endpoints |
| 4. API key auth | TWILIO_API_KEY/TWILIO_API_SECRET mismatch between shell and .env |
| 5. Environment isolation | Whether direnv is installed and .envrc is allowed |
Common Scenarios
New user gets 401 after cloning
They have TWILIO_ACCOUNT_SID from a previous project in their shell. The .env has different credentials. Shell wins → wrong account → 401.
Fix: unset TWILIO_ACCOUNT_SID TWILIO_AUTH_TOKEN or install direnv.
Regional 401 errors
User previously set TWILIO_REGION=au1 for regional testing. They commented it out in .env but the shell still has it. All API calls silently route to AU1 endpoints where US1 credentials fail.
Fix: unset TWILIO_REGION TWILIO_EDGE — commenting out .env lines doesn't unset shell vars.
MCP tools fail but CLI works
The MCP server inherits env at launch. If shell had stale vars when Claude Code started, MCP uses those. CLI reads .env fresh each invocation.
Fix: Restart Claude Code entirely after fixing env vars.
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.
- 5d ago First seen · 66 lines · 12 tokens per session scan A 0ebfa0909949
env-doctor is a skill published in the GitHub repository wittyreference/twilio-claude-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 12 tokens to every session and 600 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…