security-scan-agent

A dependency security checklist for packages your coding agent recommends installing or updating. It checks known vulnerabilities, licenses, package integrity, and suspicious code.

In plain words
What is it for?
Use it to review package suggestions, check CVEs (publicly recorded software vulnerabilities), assess supply-chain risks, and get remediation or safer-package suggestions.
Why use it?
It helps you spot security and legal risks before untrusted or vulnerable code enters your project.

Cursor rule for Cursor

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 rules/usrrname/cursorrules/security-scan-agent
Clone the repo
git clone --depth 1 https://github.com/usrrname/cursorrules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 2,477 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.02477
Opus 5 $0.00000 $0.01239
Sonnet 5 $0.00000 $0.00495
Haiku 4.5 $0.00000 $0.00248

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

Security

Grade A, and why

security-scan-agent 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 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.

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.

.cursor/rules/core/security-scan-agent.mdc · 320 lines

How it starts

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

Security Scan Agent

This rule provides comprehensive security scanning for dependencies when AI agents suggest installing them, complementing the dependency analysis rule with deep security insights including CVE analysis, license compliance, and supply chain risk assessment.

Critical Rules

  • Only trigger when AI agents suggest dependency installation or updates or the user asks for a security scan of dependencies
  • Perform deep security analysis on agent-recommended packages
  • Check for known CVEs and security advisories across multiple databases
  • Analyze license compliance and potential legal risks
  • Assess supply chain attack risks and package integrity
  • Scan for malicious code patterns and suspicious behavior
  • Provide detailed remediation steps for security issues
  • Integrate with existing security tools and CI/CD pipelines
  • Maintain security scanning logs for audit purposes
  • Alert on critical security vulnerabilities immediately
  • Suggest secure alternatives for vulnerable packages

Security Analysis Categories

CVE Analysis

  • Check against NIST NVD database
  • Cross-reference with npm security advisories
  • Analyze vulnerability severity and exploitability
  • Assess impact on application security
  • Provide patch availability information

License Compliance

  • Identify license types and restrictions
  • Check for license conflicts and incompatibilities
  • Assess commercial usage implications
  • Flag potentially problematic licenses
  • Suggest license-compatible alternatives

Supply Chain Security

  • Verify package integrity and signatures
  • Check for typosquatting and malicious packages
  • Analyze dependency tree for attack vectors
  • Assess maintainer reputation and trust
  • Monitor for suspicious package updates

filters:

  • type: agent_interaction pattern: "install|add|dependency|package|security|vulnerability"
  • type: content pattern: "(npm install|yarn add|pnpm add|install.*package|add.*dependency)"
  • type: context pattern: "agent_suggested|ai_recommended|automated_installation"

Read the full file on GitHub · 320 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. yesterday First seen · 320 lines · 0 tokens per session scan A a8dd0a465bbf

Subscribe to this mod's changes

security-scan-agent is a cursor rule published in the GitHub repository usrrname/cursorrules (10 stars, last pushed 4mo ago), licensed ISC. It costs nothing until one of its globs matches a file; then it loads 2,477 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-31.