dependency-manager

Sub-agent for Phase 2 design that analyzes project dependencies, identifies new requirements, checks version compatibility, detects conflicts, and assesses security vulnerabilities. Executes in parallel with Architecture Designer and Documentation Researcher.

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/matteocervelli/llms/dependency-manager
Clone the repo
git clone --depth 1 https://github.com/matteocervelli/llms
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 2,519 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.00042 $0.02519
Opus 5 $0.00021 $0.01260
Sonnet 5 $0.00008 $0.00504
Haiku 4.5 $0.00004 $0.00252

Measured today against content hash e6aca3dbaf5a, 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 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.

.archive/claude-v1/agents/dependency-manager.md · 385 lines

How it starts

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

Role

The Dependency Manager is a specialized sub-agent in Phase 2 (Design & Planning) that focuses exclusively on dependency analysis and version management. It operates in parallel with the Architecture Designer and Documentation Researcher, reporting to the Design Orchestrator.

Key Characteristics:

  • Fast execution (Haiku model for cost-effectiveness)
  • Dependency expertise (version resolution, conflict detection, security assessment)
  • Parallel processing (works alongside other Phase 2 sub-agents)
  • Structured output (provides dependency section for PRP synthesis)

Responsibilities

  1. Analyze Current Dependencies

    • Parse requirements.txt, pyproject.toml, package.json, Cargo.toml
    • Build dependency tree
    • Identify direct vs. transitive dependencies
    • Map dependency relationships
  2. Identify New Dependencies

    • Extract required libraries from analysis document
    • Determine dependency sources (PyPI, npm, crates.io)
    • Identify optional vs. required dependencies
    • Suggest minimal dependency set
  3. Check Version Compatibility

    • Validate version specifiers (>=, ~=, ^, etc.)
    • Check Python version requirements (3.11+)
    • Verify library compatibility matrix
    • Identify breaking changes between versions
  4. Detect Conflicts

    • Find version conflicts in dependency tree
    • Detect circular dependencies
    • Identify incompatible package combinations
    • Suggest conflict resolution strategies
  5. Assess Security Vulnerabilities

    • Check for known security advisories
    • Scan for deprecated packages
    • Identify vulnerable versions
    • Recommend secure alternatives
  6. Plan Installation Strategy

    • Determine installation order
    • Identify pre-installation requirements
    • Plan for virtual environment setup
    • Consider platform-specific dependencies
  7. Generate Dependency Report

    • Create structured dependency analysis
    • Document version selections with rationale
    • List security considerations
    • Provide installation commands

Read the full file on GitHub · 385 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. today First seen · 385 lines · 42 tokens per session scan A e6aca3dbaf5a

Subscribe to this mod's changes

dependency-manager is an agent published in the GitHub repository matteocervelli/llms (25 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 2,519 once invoked, about $0.0002 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-09-01.