dep-update

A command that finds outdated software packages in a project and updates them within selected limits. It can handle common ecosystems such as Python, Node.js, Java, and other detected package systems.

In plain words
What is it for?
Use it to apply patch or minor updates, limit changes to packages with known security advisories, include major upgrades, or preview updates without changing files.
Why use it?
Old packages may contain security problems or bug fixes, while updates can also break existing code. The command reviews changes, tests updates, and can roll back failed ones.

Command

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.

agentmods
npx agentmods add commands/alphaaiservice/cortex/dep-update
Clone the repo
git clone --depth 1 https://github.com/alphaaiservice/cortex
Per session 42 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 9,249 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
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 $0.00042 $0.09249
Opus 5 $0.00021 $0.04625
Sonnet 5 $0.00008 $0.01850
Haiku 4.5 $0.00004 $0.00925

Measured yesterday against content hash 4e4a99fcb209, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

dep-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 yesterday.

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.

echo "To remove backup: rm -rf $BACKUP_DIR"

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

commands/dep-update.md · 1,134 lines

How it starts

The opening of the file, as written. The whole thing — 1,134 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Automated Dependency Update Manager

$ARGUMENTS = optional flags for scope control (--security-only, --major, --dry-run, or combination).

Parse the arguments:

  • --security-only — Only apply packages with known CVEs/security advisories. Skip all non-security updates.
  • --major — Include major version bumps (breaking changes). Without this flag, major bumps are skipped and reported.
  • --dry-run — Analyze and report what would be updated, but make ZERO changes to any files.
  • No arguments — Apply patch and minor updates. Skip major bumps. Report everything.

Step 1: Detect Project Type and Inventory Current Dependencies

1a: Identify Package Ecosystem(s)

Scan the project root and subdirectories to determine what package ecosystems are in use.

echo "=== Detecting Project Type ==="

# Python indicators
echo "--- Python ---"
ls -la requirements*.txt 2>/dev/null
ls -la pyproject.toml 2>/dev/null
ls -la setup.py 2>/dev/null
ls -la setup.cfg 2>/dev/null
ls -la Pipfile 2>/dev/null
ls -la poetry.lock 2>/dev/null
ls -la uv.lock 2>/dev/null

# Node.js indicators
echo "--- Node.js ---"
ls -la package.json 2>/dev/null
ls -la package-lock.json 2>/dev/null
ls -la yarn.lock 2>/dev/null
ls -la pnpm-lock.yaml 2>/dev/null
ls -la bun.lockb 2>/dev/null

# Rust indicators
echo "--- Rust ---"
ls -la Cargo.toml 2>/dev/null

# Go indicators
echo "--- Go ---"
ls -la go.mod 2>/dev/null

# Java/Gradle indicators
echo "--- Java/Gradle ---"
ls -la build.gradle.kts build.gradle pom.xml 2>/dev/null
ls -la gradle/wrapper/gradle-wrapper.properties 2>/dev/null

Determine the primary and secondary ecosystems. A project may have BOTH backend and frontend dependencies (e.g., FastAPI/NestJS/Spring Boot backend + Next.js frontend). Handle each ecosystem independently.

For Java/Gradle projects, use:

  • ./gradlew dependencies to list all dependencies
  • ./gradlew dependencyUpdates (with com.github.ben-manes.versions plugin) to check for updates
  • Update versions in build.gradle.kts directly
  • Run ./gradlew build test after each update to verify

Read the full file on GitHub · 1,134 lines

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. yesterday First seen · 1,134 lines · 42 tokens per session scan B 4e4a99fcb209

Subscribe to this mod's changes

dep-update is a command published in the GitHub repository alphaaiservice/cortex (1 stars, last pushed 26d ago), licensed MIT. It adds 42 tokens to every session and 9,249 once invoked, about $0.0002 per session on Opus 5. 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.