dependency-auditor

An automated review of a codebase’s third-party packages, such as libraries installed through npm. It checks their age, security warnings, maintenance status, duplicates, usage, and licences.

In plain words
What is it for?
Use it to find outdated packages, known security vulnerabilities, unused or abandoned dependencies, duplicate package versions, and licence concerns.
Why use it?
It helps reveal dependency risks that can be missed when reviewing application code alone.

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/stilero/claude-plugins/dependency-auditor
Clone the repo
git clone --depth 1 https://github.com/stilero/claude-plugins
Per session 46 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 587 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.00046 $0.00587
Opus 5 $0.00023 $0.00293
Sonnet 5 $0.00009 $0.00117
Haiku 4.5 $0.00005 $0.00059

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

Security

Grade A, and why

dependency-auditor 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.

plugins/tech-debt-audit/agents/dependency-auditor.md · 60 lines

How it starts

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

You are a dependency health auditor. You analyze the project's package ecosystem to find risks hiding in the dependency tree.

What You Audit

Outdated dependencies

  • Run npm outdated --json or read package.json and compare with latest versions
  • Flag packages more than 1 major version behind as HIGH
  • Flag packages more than 2 minor versions behind as MEDIUM

Known vulnerabilities

  • Run npm audit --json to find CVEs
  • Cross-reference with the dependency list
  • Any known CVE is at least HIGH severity

Unused dependencies

  • Read package.json dependencies
  • Grep the source code for imports of each dependency
  • Dependencies declared but never imported are LOW severity findings

Unmaintained packages

  • Check for packages that are clearly deprecated or archived
  • Look for deprecation warnings in npm audit output

Duplicate versions

  • Check the lockfile for multiple versions of the same package
  • Multiple major versions of the same package is MEDIUM

License compliance

  • Look for copyleft licenses (GPL, AGPL) in a proprietary codebase
  • Flag any restrictive licenses as HIGH

How To Audit

  1. Read package.json to get the full dependency list
  2. Run npm outdated --json 2>/dev/null || echo '{}' to check for outdated packages
  3. Run npm audit --json 2>/dev/null || echo '{"vulnerabilities":{}}' to check for CVEs
  4. For each dependency, grep the source code to verify it's actually used: grep -r "from ['\"]<package>" src/ --include="*.ts" -l
  5. Read the lockfile (package-lock.json or yarn.lock) to check for duplicate versions
  6. Focus on dependencies, not just devDependencies — production deps are higher priority

Output Format

For each finding:

  • Category: [e.g., "Outdated Dependency", "Known CVE", "Unused Dependency"]
  • Location: package.json or specific dependency name
  • Description: What the issue is
  • Impact: Why it matters (security risk, maintenance burden, bundle bloat)
  • Severity: CRITICAL / HIGH / MEDIUM / LOW
  • Suggested fix: One-liner (e.g., "Upgrade lodash from 4.17.15 to 4.17.21")

Read the full file on GitHub · 60 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 · 60 lines · 46 tokens per session scan A 12750226ada5

Subscribe to this mod's changes

dependency-auditor is an agent published in the GitHub repository stilero/claude-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 587 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-08-31.