update-deps

update-deps is a command for Claude Code from HKTITAN/cursor-best-practices. It costs 0 tokens per session (248 once invoked), scanned A, original, MIT.

A project maintenance command that updates software packages and their locked versions. Dependencies are external libraries the project relies on.

In plain words
What is it for?
Use it to update all dependencies or selected packages, identify breaking changes, and verify the result with tests and a build.
Why use it?
It avoids updating packages by hand and checks whether the project still builds and passes its tests afterward.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: mentions AGENTS.md.

Good fit Use it to update all dependencies or selected packages, identify breaking changes, and verify the result with tests and a build.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/hktitan/cursor-best-practices/update-deps
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/HKTITAN/cursor-best-practices

Made for: Claude Code.

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.

agentmods badge for update-deps

README.md
[![agentmods](https://agentmods.dev/badge/commands/hktitan/cursor-best-practices/update-deps.svg)](https://agentmods.dev/commands/hktitan/cursor-best-practices/update-deps)
Your own site
<a href="https://agentmods.dev/commands/hktitan/cursor-best-practices/update-deps"><img src="https://agentmods.dev/badge/commands/hktitan/cursor-best-practices/update-deps.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 248 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00248
Opus 5 $0.00000 $0.00124
Sonnet 5 $0.00000 $0.00050
Haiku 4.5 $0.00000 $0.00025

Measured 7d ago against content hash 9465fd0cd77e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

update-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 7d 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.

cursor-best-practices/assets/templates/commands/update-deps.md · 24 lines

What it actually says

Update the project's dependencies and ensure the project still works.

Steps

  1. Identify package manager and lockfiles

    • e.g. package.json + package-lock.json / pnpm-lock.yaml / yarn.lock, requirements.txt / pyproject.toml, Cargo.toml, etc.
  2. Update dependencies

    • Use the appropriate command (e.g. npm update, pnpm update, pip install -U -r requirements.txt, cargo update). Prefer non-breaking updates unless I asked for major upgrades.
    • If I specified packages or scope (e.g. /update-deps lodash react), limit updates accordingly.
  3. Run tests and build

    • Run the test suite and any build step. Fix breakages (e.g. API changes, deprecated usage).
  4. Report

    • What was updated (packages, versions).
    • Any breaking changes or migration steps.
    • Test and build status.

Rules

  • Prefer patch/minor updates unless explicitly asked for major. Call out breaking changes clearly.
  • Apply project rules from .cursor/rules or AGENTS.md.
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.

  1. 7d ago First seen · 24 lines · 0 tokens per session scan A 9465fd0cd77e

Subscribe to this mod's changes

update-deps is a command published in the GitHub repository HKTITAN/cursor-best-practices (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 248 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-08-31.