Dependency Security Review

A pull-request review that examines changes to software packages and their related packages for security and compatibility risks.

In plain words
What is it for?
It reviews new, upgraded, and removed packages in package.json and checks package-lock.json changes, including large lockfile updates and added indirect dependencies.
Why use it?
It helps catch vulnerable, abandoned, unnecessary, incorrectly versioned, or breaking dependencies before they reach users.

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/continuedev/continue/dependency-security-review
Clone the repo
git clone --depth 1 https://github.com/continuedev/continue
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 420 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00013 $0.00420
Opus 5 $0.00006 $0.00210
Sonnet 5 $0.00003 $0.00084
Haiku 4.5 $0.00001 $0.00042

Measured yesterday against content hash f0b565b49fce, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Dependency Security Review scanned grade A with 1 finding 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 yesterday.

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.

Unrestricted tool accesslowExcessive agency

A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.

3. **Post-install scripts** - Dependencies with `postinstall` scripts can execute arbitrary code during `npm install`.

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

.continue/agents/dependency-security-review.md · 49 lines

What it actually says

Dependency Security Review

Review this pull request for changes to dependencies. A significant portion of PRs in this repo are automated dependency bumps (Dependabot, Snyk). This check ensures dependency changes get meaningful review.

What to Check

For Any package.json Changes

  1. New dependencies - For each newly added dependency:

    • Is it well-maintained (not abandoned)?
    • Does it have known vulnerabilities?
    • Is it the right choice, or does an existing dependency already cover this use case?
    • Is the version pinned appropriately (exact vs range)?
  2. Major version bumps - For major version upgrades:

    • Are there breaking changes that affect our usage?
    • Have the callers been updated to match the new API?
  3. Removed dependencies - For each removed dependency:

    • Are all imports/requires of this dependency also removed?
    • Is there a replacement, or was the functionality dropped?

For package-lock.json Changes

  1. Large lockfile diffs (>500 lines changed) - Flag for human review, as they may indicate a transitive dependency shift that warrants attention.

  2. New transitive dependencies - Check if the total dependency count increased significantly.

Security-Specific Concerns

  1. Packages with filesystem/network access - New dependencies that read/write files or make network requests deserve extra scrutiny since this tool runs locally on user machines.

  2. Native/binary dependencies - New native modules (node-gyp, .node binaries) increase the attack surface and build complexity.

  3. Post-install scripts - Dependencies with postinstall scripts can execute arbitrary code during npm install.

What to Do

  • If you find concerning dependency changes, add a comment explaining the concern.
  • Do NOT modify package.json or package-lock.json files directly.
  • If no dependency files were changed in this PR, do nothing.
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. yesterday First seen · 49 lines · 13 tokens per session scan A f0b565b49fce

Subscribe to this mod's changes

Dependency Security Review is an agent published in the GitHub repository continuedev/continue (35,702 stars, last pushed 2d ago), licensed Apache-2.0. It adds 13 tokens to every session and 420 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other agents, from other repositories