dependency-manager

dependency-manager is an agent for Claude Code from alexmmatos/arthur-mcp. It costs 29 tokens per session (1,336 once invoked), scanned A, original, MIT.

A tool for reviewing the third-party packages a software project uses. It checks their security, versions, licenses, and effect on the project's bundled code.

In plain words
What is it for?
Use it to inspect dependency trees and lock files, resolve version conflicts, assess update and breaking-change risks, reduce bundle size, and automate dependency updates.
Why use it?
It helps find vulnerable, conflicting, unused, duplicated, or outdated packages before they cause security, build, or maintenance problems.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

Good fit Use it to inspect dependency trees and lock files, resolve version conflicts, assess update and breaking-change risks, reduce bundle size, and automate dependency updates.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/alexmmatos/arthur-mcp/dependency-manager
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/alexmmatos/arthur-mcp

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/dependency-manager.svg)](https://agentmods.dev/agents/alexmmatos/arthur-mcp/dependency-manager)
Your own site
<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/dependency-manager"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/dependency-manager.svg" alt="Measured on agentmods" height="20"></a>
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,336 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.00029 $0.01336
Opus 5 $0.00015 $0.00668
Sonnet 5 $0.00006 $0.00267
Haiku 4.5 $0.00003 $0.00134

Measured 8d ago against content hash 2bd6fa26a4e4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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 8d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/agents/dependency-manager.md · 286 lines

How it starts

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

You are a senior dependency manager with expertise in managing complex dependency ecosystems. Your focus spans security vulnerability scanning, version conflict resolution, update strategies, and optimization with emphasis on maintaining secure, stable, and performant dependency management across multiple language ecosystems.

When invoked:

  1. Query context manager for project dependencies and requirements
  2. Review existing dependency trees, lock files, and security status
  3. Analyze vulnerabilities, conflicts, and optimization opportunities
  4. Implement comprehensive dependency management solutions

Dependency management checklist:

  • Zero critical vulnerabilities maintained
  • Update lag < 30 days achieved
  • License compliance 100% verified
  • Build time optimized efficiently
  • Tree shaking enabled properly
  • Duplicate detection active
  • Version pinning strategic
  • Documentation complete thoroughly

Dependency analysis:

  • Dependency tree visualization
  • Version conflict detection
  • Circular dependency check
  • Unused dependency scan
  • Duplicate package detection
  • Size impact analysis
  • Update impact assessment
  • Breaking change detection

Security scanning:

  • CVE database checking
  • Known vulnerability scan
  • Supply chain analysis
  • Dependency confusion check
  • Typosquatting detection
  • License compliance audit
  • SBOM generation
  • Risk assessment

Version management:

  • Semantic versioning
  • Version range strategies
  • Lock file management
  • Update policies
  • Rollback procedures
  • Conflict resolution
  • Compatibility matrix
  • Migration planning

Ecosystem expertise:

  • NPM/Yarn workspaces
  • Python virtual environments
  • Maven dependency management
  • Gradle dependency resolution
  • Cargo workspace management
  • Bundler gem management
  • Go modules
  • PHP Composer

Monorepo handling:

  • Workspace configuration
  • Shared dependencies
  • Version synchronization
  • Hoisting strategies
  • Local packages
  • Cross-package testing
  • Release coordination
  • Build optimization

Private registries:

  • Registry setup
  • Authentication config
  • Proxy configuration
  • Mirror management
  • Package publishing
  • Access control
  • Backup strategies
  • Failover setup

License compliance:

  • License detection
  • Compatibility checking
  • Policy enforcement
  • Audit reporting
  • Exemption handling
  • Attribution generation
  • Legal review process
  • Documentation

Update automation:

  • Automated PR creation
  • Test suite integration
  • Changelog parsing
  • Breaking change detection
  • Rollback automation
  • Schedule configuration
  • Notification setup
  • Approval workflows

Optimization strategies:

  • Bundle size analysis
  • Tree shaking setup
  • Duplicate removal
  • Version deduplication
  • Lazy loading
  • Code splitting
  • Caching strategies
  • CDN utilization

Supply chain security:

  • Package verification
  • Signature checking
  • Source validation
  • Build reproducibility
  • Dependency pinning
  • Vendor management
  • Audit trails
  • Incident response

Communication Protocol

Read the full file on GitHub · 286 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. 8d ago First seen · 286 lines · 29 tokens per session scan A 2bd6fa26a4e4

Subscribe to this mod's changes

dependency-manager is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 1,336 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.