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.
git clone --depth 1 https://github.com/rubenCodeforges/codeforges-claude-pluginWrote 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.
[](https://agentmods.dev/agents/rubencodeforges/codeforges-claude-plugin/dependency-analyzer)<a href="https://agentmods.dev/agents/rubencodeforges/codeforges-claude-plugin/dependency-analyzer"><img src="https://agentmods.dev/badge/agents/rubencodeforges/codeforges-claude-plugin/dependency-analyzer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/rubencodeforges/codeforges-claude-plugin/dependency-analyzer"><img src="https://agentmods.dev/badge/agents/rubencodeforges/codeforges-claude-plugin/dependency-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00060 | $0.01835 |
| Opus 5.5 | $0.00024 | $0.00734 |
| Sonnet 5.5 | $0.00012 | $0.00367 |
| Haiku 4.5 | $0.00006 | $0.00184 |
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 1mo 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.
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
- Analyze dependency files (package.json, requirements.txt, go.mod, etc.)
- Map dependency trees and relationships
- Detect circular dependencies and import cycles
- Identify security vulnerabilities and outdated packages
- Analyze bundle sizes and optimization opportunities
- Track unused dependencies for cleanup
Workflow
When analyzing dependencies:
-
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)
-
Read dependency files: Parse and understand versions, constraints
-
Analyze dependency graph: Map relationships and identify issues
-
Check for problems:
- Outdated versions
- Security vulnerabilities
- Duplicate dependencies
- Circular dependencies
- Unused dependencies
-
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
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.
- 1mo ago First seen · 324 lines · 60 tokens per session scan A 7bd9f6c73066
dependency-analyzer is an agent published in the GitHub repository rubenCodeforges/codeforges-claude-plugin (3 stars, last pushed 10mo ago), licensed MIT. It adds 60 tokens to every session and 1,835 once invoked, about $0.0002 per session on Opus 5.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.
Other agents, from other repositories
Diagnostic Pipeline
Autonomous end-to-end machinery diagnostic agent following ISO 13374.
perf
Performance audit for web applications. Bundle size, Core Web Vitals, runtime bottlenecks, N+1 queries, memory leaks, rendering inefficiencies. Framework-aware (Next.js, Vite, Webpack). Use before deploys or when things feel slow.
feasibility-check
Pre-build feasibility checker. Use when you have a spec, plan, or requirements doc and want to confirm the codebase can support it before writing code. Extracts spec assumptions (fields, endpoints, dependencies, patterns) and reports each as CONFIRMED, NOT FOUND, or CONTRADICTED with file:line references. Read-only.
gui-validator
GUI validation, debugging, and performance monitoring specialist with automated diagnostics and issue resolution.
performance-optimizer
Analyzes performance characteristics of implementations and identifies optimization opportunities for speed, efficiency, and resource usage improvements.
cpp-build-resolver
C++ build, CMake, and compilation error resolution specialist. Fixes build errors, linker issues, and template errors with minimal changes. Use when C++ builds fail.