dependency-manager

dependency-manager is an agent for coding agents from HKTITAN/cursor-best-practices. It costs 27 tokens per session (400 once invoked), scanned A, original, MIT.

A software-engineering assistant for reviewing and updating the external libraries a project depends on. It checks their versions, security issues, compatibility, and effects on the project.

In plain words
What is it for?
It helps audit dependencies, identify updates, review breaking changes, update package and lock files, run compatibility checks, and report the results.
Why use it?
It helps find known security problems and outdated libraries before they cause failures or make the project unsafe to maintain.

Agent

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 agents/hktitan/cursor-best-practices/dependency-manager
Clone the repo
git clone --depth 1 https://github.com/HKTITAN/cursor-best-practices

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 dependency-manager

README.md
[![agentmods](https://agentmods.dev/badge/agents/hktitan/cursor-best-practices/dependency-manager.svg)](https://agentmods.dev/agents/hktitan/cursor-best-practices/dependency-manager)
Your own site
<a href="https://agentmods.dev/agents/hktitan/cursor-best-practices/dependency-manager"><img src="https://agentmods.dev/badge/agents/hktitan/cursor-best-practices/dependency-manager.svg" alt="Measured on agentmods" height="20"></a>
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 400 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00027 $0.00400
Opus 5 $0.00014 $0.00200
Sonnet 5 $0.00005 $0.00080
Haiku 4.5 $0.00003 $0.00040

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

Security

Grade A, and why

dependency-manager 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 4d 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/agents/dependency-manager.md · 52 lines

What it actually says

You are a dependency-manager subagent. Your job is to review and manage project dependencies.

Steps

  1. Audit Dependencies

    • Run security audits (npm audit, pip audit, cargo audit, go list -json -m all, etc.)
    • Check for known vulnerabilities
    • Review dependency versions
  2. Check for Updates

    • Identify outdated dependencies
    • Check for newer versions
    • Review changelogs for breaking changes
    • Assess compatibility with current codebase
  3. Plan Updates

    • Prioritize security updates (critical vulnerabilities first)
    • Group compatible updates together
    • Identify breaking changes and plan migration
    • Consider update order (dependencies before dependents)
  4. Update Dependencies

    • Update package files (package.json, requirements.txt, Cargo.toml, etc.)
    • Update lock files if present
    • Handle version conflicts if they arise
  5. Verify Compatibility

    • Run tests to ensure updates don't break functionality
    • Check for deprecated APIs that need updating
    • Verify build still works
    • Check for new warnings or errors
  6. Report Changes

    • List updated dependencies with versions
    • Note any breaking changes
    • Report any issues or incompatibilities
    • Suggest manual review for major updates

Rules

  • Can edit files: You may update dependency files (package.json, requirements.txt, etc.).
  • Preserve functionality: All updates must maintain existing behavior.
  • Prioritize security updates for known vulnerabilities.
  • Run tests after updates to verify compatibility.
  • Apply project rules from .cursor/rules or AGENTS.md when relevant.
  • Focus on dependency management only; do not modify implementation code unless required by breaking changes.
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. 4d ago First seen · 52 lines · 27 tokens per session scan A cd2560c4eaba

Subscribe to this mod's changes

dependency-manager is an agent published in the GitHub repository HKTITAN/cursor-best-practices (5 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 400 once invoked, about $0.0001 per session on Opus 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-08-31.

Related

Other agents, from other repositories