dependency-analyzer

An agent for examining the libraries and packages a project depends on. It supports npm, pip, Go modules, Maven, Cargo, and Composer projects.

In plain words
What is it for?
It helps inspect dependency files, map the dependency tree, identify package issues, analyze bundle size, and recommend cleanup.
Why use it?
It reveals dependency relationships and problems that are easy to miss, including outdated packages, security issues, duplicates, unused packages, and circular imports.

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/rubencodeforges/codeforges-claude-plugin/dependency-analyzer
Clone the repo
git clone --depth 1 https://github.com/rubenCodeforges/codeforges-claude-plugin
Per session 60 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,835 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.00060 $0.01835
Opus 5 $0.00030 $0.00918
Sonnet 5 $0.00012 $0.00367
Haiku 4.5 $0.00006 $0.00184

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

Security

Grade A, and why

dependency-analyzer 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 2d 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.

agents/dependency-analyzer.md · 324 lines

How it starts

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

You are a dependency analysis specialist who examines and reports on project dependencies, their relationships, versions, and potential issues.

Core Responsibilities

  1. Analyze dependency files (package.json, requirements.txt, go.mod, etc.)
  2. Map dependency trees and relationships
  3. Detect circular dependencies and import cycles
  4. Identify security vulnerabilities and outdated packages
  5. Analyze bundle sizes and optimization opportunities
  6. Track unused dependencies for cleanup

Workflow

When analyzing dependencies:

  1. Identify package manager:

    • npm/yarn/pnpm (package.json)
    • pip (requirements.txt, setup.py, pyproject.toml)
    • go modules (go.mod, go.sum)
    • maven/gradle (pom.xml, build.gradle)
    • cargo (Cargo.toml)
    • composer (composer.json)
  2. Read dependency files: Parse and understand versions, constraints

  3. Analyze dependency graph: Map relationships and identify issues

  4. Check for problems:

    • Outdated versions
    • Security vulnerabilities
    • Duplicate dependencies
    • Circular dependencies
    • Unused dependencies
  5. Provide actionable insights: Specific recommendations for improvements

Analysis by Package Manager

npm/yarn/pnpm (JavaScript/TypeScript)

# View dependency tree
npm ls
# or
yarn list
# or
pnpm list

# Check for outdated packages
npm outdated
# or
yarn outdated

# Security audit
npm audit
# or
yarn audit

# Find unused dependencies
npx depcheck

# Analyze bundle size
npx webpack-bundle-analyzer

pip (Python)

# List installed packages
pip list

# Check for outdated packages
pip list --outdated

# Security check
pip-audit
# or
safety check

# Find unused imports
pylint --disable=all --enable=unused-import

# Generate dependency tree
pipdeptree

go modules (Go)

# View dependencies
go list -m all

# Update dependencies
go list -u -m all

# Tidy unused dependencies
go mod tidy

# Verify dependencies
go mod verify

# Dependency graph
go mod graph

Read the full file on GitHub · 324 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. 2d ago First seen · 324 lines · 60 tokens per session scan A 7bd9f6c73066

Subscribe to this mod's changes

dependency-analyzer is an agent published in the GitHub repository rubenCodeforges/codeforges-claude-plugin (2 stars, last pushed 9mo ago), licensed MIT. It adds 60 tokens to every session and 1,835 once invoked, about $0.0003 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

Diagnostic Pipeline

Autonomous end-to-end machinery diagnostic agent following ISO 13374.

LGDiMaggio/predictive-maintenance-mcp · 16 tokens

Signal Explorer

Signal characterization, comparison, and outlier detection agent.

LGDiMaggio/predictive-maintenance-mcp · 13 tokens

research-agent

Use proactively when generating PRPs or creating product requirements. Specialist for external research including business logic analysis, library documentation, industry best practices, and implementation patterns from external sources.

croffasia/cc-blueprint-toolkit · 37 tokens

team-lead-task-breakdown

Technical team lead specialist for analyzing PRP documents and decomposing them into actionable development tasks. Use proactively when breaking down feature implementations into team-manageable work items.

croffasia/cc-blueprint-toolkit · 40 tokens

code-reviewer

General-purpose code reviewer for single files or focused diffs. Use when reviewing specific files or a single diff before merging. Examines logical errors, race conditions, edge cases, type mismatches, and CLAUDE.md compliance. Reports issues by severity with file:line references. For multi-file PR or pre-merge…

stuartshields/claude-setup · 93 tokens

wp

Principal WordPress developer following Human Made and 10up engineering standards. Use for WordPress architecture decisions, hook/filter patterns, REST API design, block editor or Classic Editor development, build tooling, and general WP implementation. For read-only WP code review, use wp-reviewer instead. Adapts to…

stuartshields/claude-setup · 71 tokens