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/rafaelkamimura/claude-tools/deps-updategit clone --depth 1 https://github.com/rafaelkamimura/claude-toolsWrote 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/rafaelkamimura/claude-tools/deps-update)<a href="https://agentmods.dev/commands/rafaelkamimura/claude-tools/deps-update"><img src="https://agentmods.dev/badge/commands/rafaelkamimura/claude-tools/deps-update.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.1 | $0.00000 | $0.03174 |
| Opus 5 | $0.00000 | $0.01587 |
| Sonnet 5 | $0.00000 | $0.00635 |
| Haiku 4.5 | $0.00000 | $0.00317 |
Grade B, and why
deps-update scanned grade B with 1 finding 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 6d 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf node_modules Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 540 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Manager
Comprehensive dependency updater that checks for outdated packages, tests compatibility, manages security patches, and handles lock files.
Purpose
- Check for outdated packages
- Test compatibility before updating
- Security vulnerability patches
- Generate update changelog
- Lock file management
Workflow
Step 1: Update Strategy
-
STOP → "Select update strategy:"
1. Security only - Critical patches only 2. Patch updates - Bug fixes (1.0.x) 3. Minor updates - New features (1.x.0) 4. Major updates - Breaking changes (x.0.0) 5. Interactive - Choose each update 6. Full update - Everything latest Choose strategy (1-6): -
Update Options
- STOP → "Run tests after update? (y/n):"
- STOP → "Create separate branch? (y/n):"
- STOP → "Update lock files? (y/n):"
- STOP → "Generate changelog? (y/n):"
Step 2: Dependency Analysis
Package Managers Detection
# Detect package managers
managers=()
[ -f "package.json" ] && managers+=("npm")
[ -f "yarn.lock" ] && managers+=("yarn")
[ -f "pnpm-lock.yaml" ] && managers+=("pnpm")
[ -f "requirements.txt" ] && managers+=("pip")
[ -f "Pipfile" ] && managers+=("pipenv")
[ -f "poetry.lock" ] && managers+=("poetry")
[ -f "go.mod" ] && managers+=("go")
[ -f "Cargo.toml" ] && managers+=("cargo")
[ -f "Gemfile" ] && managers+=("bundler")
[ -f "composer.json" ] && managers+=("composer")
Outdated Package Check
JavaScript/Node.js
# npm
npm outdated --json
# yarn
yarn outdated --json
# pnpm
pnpm outdated --format json
Python
# pip
pip list --outdated --format json
# poetry
poetry show --outdated
# pipenv
pipenv update --outdated
Go
go list -u -m -json all
Step 3: Security Audit
Vulnerability Scanning
// npm/yarn security audit
async function securityAudit() {
const audit = await exec('npm audit --json');
const report = JSON.parse(audit);
return {
critical: report.metadata.vulnerabilities.critical,
high: report.metadata.vulnerabilities.high,
moderate: report.metadata.vulnerabilities.moderate,
low: report.metadata.vulnerabilities.low,
packages: report.vulnerabilities
};
}
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.
- 6d ago First seen · 540 lines · 0 tokens per session scan B 621da3150d68
deps-update is a command published in the GitHub repository rafaelkamimura/claude-tools (10 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,174 tokens. A static security scan graded it B with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.