dependency-scanner

An agent that reviews the npm packages a JavaScript or TypeScript project depends on. npm is the package manager commonly used for these projects.

In plain words
What is it for?
Use it to run dependency security and license checks, review package updates, measure dependency counts, and identify packages worth removing or replacing.
Why use it?
It reveals known security problems, outdated packages, unnecessary dependencies, and packages that make installation significantly larger. It does not install or remove packages without approval.

Agent for Claude Code

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/ruah-dev/ruah-orch/dependency-scanner
Clone the repo
git clone --depth 1 https://github.com/ruah-dev/ruah-orch

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 169 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.00000 $0.00169
Opus 5 $0.00000 $0.00084
Sonnet 5 $0.00000 $0.00034
Haiku 4.5 $0.00000 $0.00017

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

Security

Grade A, and why

dependency-scanner 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 3d 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.

.claude/agents/dependency-scanner.md · 27 lines

What it actually says

Dependency Scanner Agent

Audit npm dependencies for vulnerabilities and license issues.

Commands

npm audit 2>/dev/null || echo "No dependencies to audit"
npm ls --all 2>/dev/null || echo "No dependencies installed"

Behavior

  1. Run npm audit for known vulnerabilities
  2. Check for outdated packages: npm outdated
  3. Verify no unnecessary dependencies (project prefers zero runtime deps)
  4. Flag any dependency that adds significant install size
  5. Report: total deps, vulnerabilities (critical/high/moderate/low), recommendations

Isolation

isolation: worktree

Boundaries

  • Operate only within this repository
  • No destructive system commands
  • No network access beyond npm registry
  • No permission escalation
  • Do not install or remove packages without approval
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. 3d ago First seen · 27 lines · 0 tokens per session scan A 2af8eae30077

Subscribe to this mod's changes

dependency-scanner is an agent published in the GitHub repository ruah-dev/ruah-orch (11 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 169 tokens. 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-30.