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.
git clone --depth 1 https://github.com/travisjneuman/.claudeWrote 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/travisjneuman/.claude/deps-update)<a href="https://agentmods.dev/commands/travisjneuman/.claude/deps-update"><img src="https://agentmods.dev/badge/commands/travisjneuman/.claude/deps-update/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/travisjneuman/.claude/deps-update"><img src="https://agentmods.dev/badge/commands/travisjneuman/.claude/deps-update.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00005 | $0.01303 |
| Opus 5.5 | $0.00002 | $0.00521 |
| Sonnet 5.5 | $0.00001 | $0.00261 |
| Haiku 4.5 | $0.00001 | $0.00130 |
Grade A, and why
deps-update 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 13d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Update Manager
Checks for outdated dependencies, identifies security advisories, checks compatibility, and creates an update plan.
Execution Flow
Step 1: Detect Package Manager
[ -f "pnpm-lock.yaml" ] && echo "PNPM"
[ -f "yarn.lock" ] && echo "YARN"
[ -f "bun.lockb" ] && echo "BUN"
[ -f "package-lock.json" ] && echo "NPM"
[ -f "requirements.txt" ] || [ -f "pyproject.toml" ] && echo "PIP"
[ -f "Pipfile" ] && echo "PIPENV"
[ -f "poetry.lock" ] && echo "POETRY"
[ -f "go.sum" ] && echo "GO"
[ -f "Cargo.lock" ] && echo "CARGO"
[ -f "Gemfile.lock" ] && echo "BUNDLER"
Step 2: Check Outdated Dependencies
Mode: {{mode}} (default: check)
# Node.js
npm outdated --json 2>/dev/null
# Python
pip list --outdated --format=json 2>/dev/null
# Go
go list -u -m all 2>/dev/null
# Rust
cargo outdated 2>/dev/null
Display as structured table:
Outdated Dependencies
---------------------
Package Current Wanted Latest Type
react 18.2.0 18.3.1 19.0.0 dependencies
typescript 5.3.3 5.4.5 5.7.2 devDependencies
@types/node 20.10.0 20.14.2 22.10.1 devDependencies
eslint 8.56.0 8.57.1 9.15.0 devDependencies
Step 3: Security Advisory Check
# Node.js
npm audit --json 2>/dev/null
# Python
pip-audit --format=json 2>/dev/null
# Go
govulncheck ./... 2>/dev/null
# Rust
cargo audit --json 2>/dev/null
Flag security-critical updates:
Security Advisories
-------------------
CRITICAL:
[email protected] -> 4.18.2 (CVE-2024-XXXX: Open Redirect)
[email protected] -> 9.0.0 (CVE-2022-23529: Algorithm Confusion)
HIGH:
[email protected] -> 1.6.0 (CVE-2023-45857: CSRF Bypass)
Step 4: Run by Mode
check (default)
Report only. No changes made. Display outdated deps and advisories.
security
Update only packages with known security vulnerabilities:
# Node.js
npm audit fix
# Python
pip install --upgrade <package-with-advisory>
# Go
go get <module>@latest
# Rust
cargo update <crate>
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.
- 13d ago Changed · -11 lines scan B → A 05a72d4d72cf
- 27d ago Changed · -13 lines 6d88172f312b
- 1mo ago First seen · 241 lines · 5 tokens per session scan B 60149332509d
deps-update is a command published in the GitHub repository travisjneuman/.claude (106 stars, last pushed yesterday), licensed MIT. It adds 5 tokens to every session and 1,303 once invoked, about $0.0000 per session on Opus 5.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-09-03.
Other commands, from other repositories
dev-tdd
Implements a feature by following the TDD (Test-Driven Development) cycle.
qa-tech-debt
Identification and prioritization of technical debt in the codebase.
work-flow-feature
Complete workflow for developing a new feature, from exploration to merge.
qa-automation
Set up a comprehensive test automation strategy.
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.