A dependency update checker for projects using npm, Yarn, or pnpm. It groups available updates as patch, minor, or major changes and can apply patch updates.

Use it to scan dependencies, apply patch updates, review minor or major releases, read breaking-change notes, run tests, and address security advisories.

It separates lower-risk updates from changes that may break the project, so you can update libraries without treating every version change the same way.

deps-update — Command for Claude Code by fatihkan

Install

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.

Clone the repo

git clone --depth 1 https://github.com/fatihkan/badi

Made for: Claude Code.

Or install badi, the plugin that ships this one along with the rest of its 81 skills, 86 commands, 30 agents, 7 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/fatihkan/badi/deps-update.svg)](https://agentmods.dev/commands/fatihkan/badi/deps-update)

Your own site

<a href="https://agentmods.dev/commands/fatihkan/badi/deps-update"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/deps-update.svg" alt="Measured on agentmods" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 492 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00492
Opus 5	$0.00000	$0.00246
Sonnet 5	$0.00000	$0.00098
Haiku 4.5	$0.00000	$0.00049

Measured today against content hash 50de8bc02b98, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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 today.

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.

.claude/commands/deps-update.md · 73 lines

What it actually says

Safe dependency update analysis. Patch/minor/major categorization with optional automatic patch application.

Required Tools

Bash (badi dev deps)

Procedure

Step 1: Scan

badi dev deps

The package manager (npm/yarn/pnpm) is auto-detected.

Step 2: Categories

Every update falls into:

Patch (1.2.X) — Safe, auto-applicable
Minor (1.X.0) — New features, tests required
Major (X.0.0) — Breaking-change potential, manual review

Step 3: Auto-Apply Patches

badi dev deps --apply-patch

Applies only the patch level (the safest).

Step 4: Minor/Major Strategy

Minor:

npm update [package]
npm test

Major:

Read the changelog (npmjs.com/package/X)
Check the breaking-change notes
Update one at a time: npm install package@latest
Full test suite

Step 5: Security Priority

If a critical CVE exists:

npm audit
npm audit fix              # Patch + minor auto
npm audit fix --force      # Including major (risky)

Step 6: Supply-Chain Cooldown

A freshly published version is the highest-risk window for a compromised package (a hijacked maintainer account ships malware, and it is caught days later). Prefer your package manager's native minimum-release-age gate over pulling @latest the day it ships: npm (minimumReleaseAge in .npmrc, npm 11+), pnpm (minimumReleaseAge), yarn (npmMinimalAgeGate), or bun (--minimum-release-age). Let a version age a few days before adopting it — badi does not reimplement this; point at the native flag.

Step 7: Weekly Routine

# Monday morning
badi dev deps
badi dev deps --apply-patch   # Apply the patches
npm test                       # Did the tests pass
git add package-lock.json
git commit -m "chore(deps): patch updates"

Example

/deps-update
/deps-update --apply

Changes

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.

today First seen · 73 lines · 0 tokens per session scan A 50de8bc02b98

Subscribe to this mod's changes

deps-update is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 492 tokens. 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-06.

Security agents ai-workflow cli developer-tools hooks

deps-update