dependency-audit

dependency-audit is a cursor rule for Cursor from briiirussell/cybersecurity-skills. It costs 92 tokens per session (2,976 once invoked), scanned A, original, MIT.

A security review of a project's packages, frameworks, programming languages, runtimes, and development tools. It checks for known vulnerabilities called CVEs and unsafe supply-chain practices.

In plain words
What is it for?
Use it to inspect package manifests, lock files, framework versions, language runtimes, Docker bases, infrastructure providers, and CI/CD tools.
Why use it?
It helps identify outdated or compromised components before they create security problems.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Use it to inspect package manifests, lock files, framework versions, language runtimes, Docker bases, infrastructure providers, and CI/CD tools.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/briiirussell/cybersecurity-skills/dependency-audit
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.

Clone the repo
git clone --depth 1 https://github.com/briiirussell/cybersecurity-skills

Made for: Cursor.

Wrote 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.

agentmods badge for dependency-audit

README.md
[![agentmods](https://agentmods.dev/badge/rules/briiirussell/cybersecurity-skills/dependency-audit/github.svg)](https://agentmods.dev/rules/briiirussell/cybersecurity-skills/dependency-audit)
Your own site
<a href="https://agentmods.dev/rules/briiirussell/cybersecurity-skills/dependency-audit"><img src="https://agentmods.dev/badge/rules/briiirussell/cybersecurity-skills/dependency-audit/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.

agentmods 80×15 button for dependency-audit

Your own site · 80×15
<a href="https://agentmods.dev/rules/briiirussell/cybersecurity-skills/dependency-audit"><img src="https://agentmods.dev/badge/rules/briiirussell/cybersecurity-skills/dependency-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 92 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,976 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00092 $0.02976
Opus 5 $0.00046 $0.01488
Sonnet 5 $0.00018 $0.00595
Haiku 4.5 $0.00009 $0.00298

Measured 9d ago against content hash 31936d650517, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

dependency-audit 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 9d 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.

adapters/cursor/dependency-audit.mdc · 281 lines

How it starts

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

Dependency Audit — Framework, Package, and Toolchain Security

Audit project dependencies, frameworks, language runtimes, and dev tools for known vulnerabilities (CVEs), security anti-patterns, and supply chain risks.

Methodology

Step 1: Inventory the Stack

Identify everything in use — not just direct dependencies but the full chain:

Package manifests — read and catalog:

Node/JS:    package.json, package-lock.json, yarn.lock, pnpm-lock.yaml
Python:     requirements.txt, Pipfile.lock, pyproject.toml, poetry.lock
Ruby:       Gemfile, Gemfile.lock
Go:         go.mod, go.sum
Rust:       Cargo.toml, Cargo.lock
Java:       pom.xml, build.gradle
PHP:        composer.json, composer.lock
.NET:       *.csproj, packages.config

Framework and runtime versions:

  • Check framework version (Next.js, Django, Rails, Spring, Laravel, Express, etc.)
  • Check language/runtime version (Node.js, Python, Ruby, Go, Java, PHP, .NET)
  • Check infrastructure tools (Docker base images, Terraform providers, Kubernetes versions)

Dev tools and CI/CD:

  • Check CI/CD pipeline configs (.github/workflows, .gitlab-ci.yml, Jenkinsfile)
  • Check pre-commit hooks, linters, formatters
  • Check container base images and their update status
  • Check IaC tool versions (Terraform, Pulumi, CDK)

Edge cases in package manifests:

  • optionalDependencies — installed but not audited by default
  • peerDependencies — version range may not match what's installed
  • overrides / yarn resolutions / pnpm overrides — check if used to silence advisories rather than fix them
  • Monorepos: read every packages/*/package.json and apps/*/package.json, not just the root
  • engines field — older-than-LTS Node makes other audits moot

Step 2: Run Automated Audit Tools

Run the appropriate audit command for the project:

# Node.js
npm audit --json                # full structured output
npm audit --omit=dev --json     # production-only: filters dev/build-time vulns
# Compare the two — vulns only in dev/build tooling do not ship to users
# and should be triaged as lower priority. Don't bury this in the report.

# Python
pip audit          # If pip-audit installed
safety check       # If safety installed

# Ruby
bundle audit

# Go
govulncheck ./...

# Rust
cargo audit

# PHP
composer audit

# .NET
dotnet list package --vulnerable

# Docker
docker scout cves <image>
trivy image <image>

# General (if Trivy is available)
trivy fs .

Read the full file on GitHub · 281 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. 9d ago First seen · 281 lines · 92 tokens per session scan A 31936d650517

Subscribe to this mod's changes

dependency-audit is a cursor rule published in the GitHub repository briiirussell/cybersecurity-skills (384 stars, last pushed 3mo ago), licensed MIT. It adds 92 tokens to every session and 2,976 once invoked, about $0.0005 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-30.