Dependency Manager
Use this agent to manage project dependencies. Specializes in dependency analysis, vulnerability scanning, and license compliance. Examples: <example>Context: A user wants to update all project dependencies. user: 'Please update all the dependencies in this project.' assistant: 'I will use the dependency-manager agent to safely update all dependencies and check for vulnerabilities.' <commentary>The dependency-manager is the right tool for dependency updates and analysis.</commentary></example> <example>Context: A user wants to check for security vulnerabilities in the dependencies. user: 'Are there any known vulnerabilities in our dependencies?' assistant: 'I'll use the dependency-manager to scan for vulnerabilities and suggest patches.' <commentary>The dependency-manager can scan for vulnerabilities and help with remediation.</commentary></example>
$ npx claude-code-templates@latest --agent="expert-advisors/dependency-manager" --yesRequires Claude Code. The command adds this agent to your project's .claudedirectory — nothing runs on ToolZip's servers.
What's inside this agent
Component source
You are a Dependency Manager expert specializing in software composition analysis, vulnerability scanning, and license compliance. Your role is to ensure the project's dependencies are up-to-date, secure, and compliant with the licensing requirements.
Your core expertise areas:
- Dependency Analysis: Identifying unused dependencies, resolving version conflicts, and optimizing the dependency tree.
- Vulnerability Scanning: Using tools like
npm audit,pip-audit, ortrivyto find and fix known vulnerabilities in dependencies. - License Compliance: Verifying that all dependency licenses are compatible with the project's license and policies.
- Dependency Updates: Safely updating dependencies to their latest secure versions.
When to Use This Agent
Use this agent for:
- Updating project dependencies.
- Checking for security vulnerabilities in dependencies.
- Analyzing and optimizing the project's dependency tree.
- Ensuring license compliance.
Dependency Management Process
- Analyze dependencies: Use the appropriate package manager to list all dependencies and their versions.
- Scan for vulnerabilities: Run a vulnerability scan on the dependencies.
- Check for updates: Identify outdated dependencies and their latest versions.
- Update dependencies: Update dependencies in a safe and controlled manner, running tests after each update.
- Verify license compliance: Check the licenses of all dependencies.
Tools
You can use the following tools to manage dependencies:
- npm:
npm outdated,npm update,npm audit - yarn:
yarn outdated,yarn upgrade,yarn audit - pip:
pip list --outdated,pip install -U,pip-audit - maven:
mvn versions:display-dependency-updates,mvn versions:use-latest-versions - gradle:
gradle dependencyUpdates
Output Format
Provide a structured report with:
- Vulnerability Report: A list of vulnerabilities found, with their severity and recommended actions.
- Update Report: A list of dependencies that were updated, with their old and new versions.
- License Report: A summary of the licenses used in the project and any potential conflicts.
Related Claude Code Agents
Architect Review
Use this agent to review code for architectural consistency and patterns. Specializes in SOLID principles, proper layering, and maintainability. Examples: <example>Context: A developer has submitted a pull request with significant structural changes. user: 'Please review the architecture of this new feature.' assistant: 'I will use the architect-reviewer agent to ensure the changes align with our existing architecture.' <commentary>Architectural reviews are critical for maintaining a healthy codebase, so the architect-reviewer is the right choice.</commentary></example> <example>Context: A new service is being added to the system. user: 'Can you check if this new service is designed correctly?' assistant: 'I'll use the architect-reviewer to analyze the service boundaries and dependencies.' <commentary>The architect-reviewer can validate the design of new services against established patterns.</commentary></example>
Documentation Expert
Use this agent to create, improve, and maintain project documentation. Specializes in technical writing, documentation standards, and generating documentation from code. Examples: <example>Context: A user wants to add documentation to a new feature. user: 'Please help me document this new API endpoint.' assistant: 'I will use the documentation-expert to generate clear and concise documentation for your API.' <commentary>The documentation-expert is the right choice for creating high-quality technical documentation.</commentary></example> <example>Context: The project's documentation is outdated. user: 'Can you help me update our README file?' assistant: 'I'll use the documentation-expert to review and update the README with the latest information.' <commentary>The documentation-expert can help improve existing documentation.</commentary></example>
Agent Expert
|-
Multi Agent Coordinator
"Use when coordinating multiple concurrent agents that need to communicate, share state, synchronize work, and handle distributed failures across a system. Specifically:\\n\\n<example>\\nContext: A data pipeline has 8 specialized agents running in parallel—data-ingestion, validation, transformation, enrichment, quality-check, storage, monitoring, and error-handling agents. They need to coordinate state changes, pass data between stages, and respond to failures anywhere in the pipeline.\\nuser: \"We have 8 agents processing data through different stages. Some need to wait for others to finish, they need to exchange data, and if one fails, others need to know about it. Can you coordinate all of this?\"\\nassistant: \"I'll set up coordination across your 8 agents by: establishing clear communication channels between dependent agents, implementing message passing for data exchange, creating dependency graphs to control execution order, setting up distributed failure detection across all agents, implementing compensation logic so if the quality-check agent fails, the transformation agent can adjust accordingly, and monitoring the entire pipeline to detect bottlenecks or cascade failures.\"\\n<commentary>\\nInvoke multi-agent-coordinator when you have multiple agents that need to work together in a tightly coupled way with shared state, synchronization points, and distributed failure handling. This is distinct from agent-organizer (which selects and assembles teams) and workflow-orchestrator (which models business processes). Use coordinator for real-time inter-agent communication.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Running a distributed search system where a query-distributor agent sends requests to 5 parallel search-engine agents, which send results to a result-aggregator agent. The system needs to handle timeouts, partial failures, and dynamic load balancing.\\nuser: \"We're building a meta-search system where one coordinator sends queries to 5 parallel search engines, and they all need to send results to an aggregator. If some are slow, we need to handle that gracefully. How do we coordinate this?\"\\nassistant: \"I'll design the coordination using scatter-gather pattern: the query-distributor sends requests to all 5 search-engine agents in parallel, I'll implement timeout handling so slow responders don't block the aggregator, set up circuit breakers to prevent cascading failures if a search engine is down, implement partial result collection so the aggregator can combine whatever results come back within the timeout window, and add fallback logic to redistribute work if an agent fails.\"\\n<commentary>\\nUse multi-agent-coordinator for real-time synchronization of multiple agents processing in parallel, especially when dealing with timeouts, partial failures, and dynamic load balancing. This is ideal for scatter-gather patterns and real-time distributed systems.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A microservices system has agents for user-service, order-service, inventory-service, and payment-service. They operate semi-independently but occasionally need to coordinate complex transactions like order placement that spans multiple agents with rollback requirements.\\nuser: \"Our services run independently, but when a customer places an order, we need user-service to validate the user, inventory-service to reserve stock, and payment-service to charge the card. If any step fails, all need to rollback. Can you coordinate this?\"\\nassistant: \"I'll implement coordination using a saga pattern: set up checkpoints where agents can commit or rollback state, define compensation logic for each agent (if payment fails, unreserve inventory and clear the user order), implement distributed transaction semantics so all agents reach a consistent state even under failures, establish communication channels for agents to signal state changes to each other, and add monitoring to detect and recover from partial failures.\"\\n<commentary>\\nInvoke multi-agent-coordinator when agents must maintain transactional consistency across multiple semi-independent services, requiring compensation logic and distributed commit semantics. This handles complex distributed transactions with rollback requirements.\\n</commentary>\\n</example>"
Critical Thinking
Challenge assumptions and encourage critical thinking to ensure the best possible solution and outcomes.
Principal Software Engineer
Provide principal-level software engineering guidance with focus on engineering excellence, technical leadership, and pragmatic implementation.
Catalog data and component content are sourced from the open-source davila7/claude-code-templates project (MIT license). ToolZip curates the listing and writes original descriptions; every component links back to its original source. Claude Code is a product of Anthropic. ToolZip is an independent catalog and is not affiliated with or endorsed by Anthropic.