A dependency scanner that checks the packages a project uses against the OSV database, a public database of known software vulnerabilities. It can also estimate whether vulnerable code is actually referenced by the project.

Use it to scan a project or dependency file, triage vulnerability reachability, group findings by severity, and plan remediation.

It helps distinguish a list of reported package vulnerabilities from issues that may reach your code. This supports decisions about upgrades, suppressions, or continued monitoring.

osv-scanner — Skill for Claude Code by alejandrosaenz117

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.

Any agent

npx skills add alejandrosaenz117/bonfires-marketplace --skill osv-scanner

Clone the repo

git clone --depth 1 https://github.com/alejandrosaenz117/bonfires-marketplace

Made for: Claude Code.

Or install osv-scanner, the plugin that ships this one along with the rest of its 1 skill, 2 commands.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/alejandrosaenz117/bonfires-marketplace/osv-scanner/github.svg)](https://agentmods.dev/skills/alejandrosaenz117/bonfires-marketplace/osv-scanner)

Your own site

<a href="https://agentmods.dev/skills/alejandrosaenz117/bonfires-marketplace/osv-scanner"><img src="https://agentmods.dev/badge/skills/alejandrosaenz117/bonfires-marketplace/osv-scanner/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/alejandrosaenz117/bonfires-marketplace/osv-scanner"><img src="https://agentmods.dev/badge/skills/alejandrosaenz117/bonfires-marketplace/osv-scanner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,277 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.

Model	Per session	Once invoked
Fable 5.1	$0.00071	$0.01277
Opus 5	$0.00036	$0.00639
Sonnet 5	$0.00014	$0.00255
Haiku 4.5	$0.00007	$0.00128

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

Security

Grade A, and why

osv-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 12d 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/osv-scanner/skills/osv-scanner/SKILL.md · 118 lines

How it starts

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

Scan Dependencies for Vulnerabilities

Scans a project's dependencies for known vulnerabilities using the OSV database.

The user is asking about dependency security. Help them identify vulnerable packages and estimate which vulnerabilities actually reach their code.

Your Task

Identify the scanning scope: Confirm which directory or file to scan (default to workspace root)
Choose scan mode: Decide between quick scan (list vulnerabilities) or reachability triage (estimate which vulnerabilities your code actually calls)
Scan dependencies: Use appropriate tool (scan or triage)
Report findings: Present results grouped by severity, with actionable next steps
Suggest remediation: Recommend upgrades, suppression, or monitoring based on reachability

Decision Tree: Scan vs. Triage

Do you need to know if vulnerable code is *actually called* in your project?
│
├─→ YES (or unsure): Use TRIAGE
│   ├─ Shows: FOUND_IN_SOURCE, UNCERTAIN, NOT_FOUND_IN_GREP
│   ├─ Time: ~2-5 min (grep-based reachability analysis)
│   ├─ When: Deciding whether to upgrade or ignore a CVE
│   ├─ Example: "We have 42 vulnerabilities, but triage shows only 3 are
│   │           actually called — we can suppress the other 39 safely."
│   └─ Command: `/osv-scanner triage [path]`
│
└─→ NO (just need the list): Use SCAN
    ├─ Shows: All vulnerabilities, sorted by severity
    ├─ Time: <30 seconds
    ├─ When: Compliance/audit inventory, rapid security posture check
    ├─ Example: "Report all CVEs in dependencies for the board."
    └─ Command: `/osv-scanner scan [path]`

Output Format

Scan Output

Present findings in severity tiers (CRITICAL, HIGH, MEDIUM, LOW, INFO) with:

Package name and current version
Vulnerability ID and CVSS score
Advisory summary (1-2 sentences)
Link to full advisory
Remediation (upgrade version or suppress reason)

Example (abbreviated):

CRITICAL (2 vulnerabilities)
├─ express 4.17.1
│  ├─ CVE-2022-24999 (CVSS 7.5)
│  │  Open Redirect in query parser
│  │  Fix: Upgrade to express 4.18.0+
│  │  https://osv.dev/CVE-2022-24999
│  └─ CVE-2024-1086 (CVSS 8.1)
│     Authentication bypass in middleware
│     Fix: Upgrade to express 4.21.0+

HIGH (5 vulnerabilities)
├─ lodash 4.17.20
│  ├─ CVE-2021-23337 (CVSS 6.1)
│  │  Prototype pollution in defaultsDeep
│  │  Fix: Upgrade to lodash 4.17.21+
│  │  https://osv.dev/CVE-2021-23337

Read the full file on GitHub · 118 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.

12d ago First seen · 118 lines · 71 tokens per session scan A 130b25418365

Subscribe to this mod's changes

osv-scanner is a skill published in the GitHub repository alejandrosaenz117/bonfires-marketplace (4 stars, last pushed 12d ago), licensed MIT. It adds 71 tokens to every session and 1,277 once invoked, about $0.0004 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.

Claude Code Security adversarial-testing architecture plugin-marketplace

architecture-diagram

Dark-themed SVG architecture/cloud/infra diagrams as HTML.

mateaix/mateclaw · 15 tokens

modular-skills

Build composable skill modules with hub-and-spoke loading. Use when token budget is tight.

athola/claude-night-market · 24 tokens

studio

Architecture Studio control plane — initialize or inspect a studio workspace, create and register projects, or route an architecture/AEC task to the right agent or skill. Use when the user runs /as:studio, asks to set up or open their studio, manage its projects, or describes a task without naming a skill.

AlpacaLabsLLC/skills-for-architects · 65 tokens

osv-scanner