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/check-depsgit 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/check-deps)<a href="https://agentmods.dev/commands/wittyreference/twilio-claude-plugin/check-deps"><img src="https://agentmods.dev/badge/commands/wittyreference/twilio-claude-plugin/check-deps.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.00022 | $0.00366 |
| Opus 5 | $0.00011 | $0.00183 |
| Sonnet 5 | $0.00004 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
check-deps 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.
What it actually says
Check all package.json files for outdated dependencies and apply safe bumps.
Check
Run ./scripts/check-deps.sh --force to bypass cache and check now. Report the output to the user.
Then read the digest file at .update-cache/deps-digest.md and present the findings.
Apply Safe Bumps
If the user wants to apply safe bumps (within declared semver range):
- Run
npm updatein each directory that has outdated packages - For TypeScript packages, verify compilation:
npx tsc --noEmit - For the MCP server (
twilio/), also runnpm run build - Commit all lock file changes with a descriptive message listing what was bumped
Major Upgrades
For packages with major version jumps, present them separately with a recommendation:
- Review changelog — link to the package's changelog/release notes
- Check breaking changes — note known migration concerns
- Defer or adopt — recommend based on risk vs. benefit
Known major upgrade concerns:
jest29→30: Test runner migration, possible config changestypescript5→6: Compiler changes, checktsconfig.jsoncompatzod3→4: Schema API changes, affects MCP server + feature-factorydotenv16→17: Requiresquiet: trueto suppress stdout logging@anthropic-ai/sdk0.x: Pre-1.0, any minor bump can break
Arguments
<user_request> $ARGUMENTS </user_request>
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 · 42 lines · 22 tokens per session scan A 56babeb47168
check-deps is a command published in the GitHub repository wittyreference/twilio-claude-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 22 tokens to every session and 366 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.