cve-lookup

cve-lookup is a skill for Claude Code, Codex from woohyun212/security-skill. It costs 25 tokens per session (2,117 once invoked), scanned B, original, MIT.

A lookup tool for CVEs using the NIST National Vulnerability Database. A CVE is a public identifier for a specific software vulnerability, and the lookup includes severity scores, affected products, and references.

In plain words
What is it for?
Use it to investigate a CVE, validate scan findings, check affected products, and gather information for a vulnerability report.
Why use it?
It provides official vulnerability details needed to understand risk, confirm affected versions, and plan fixes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to investigate a CVE, validate scan findings, check affected products, and gather information for a vulnerability report.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/woohyun212/security-skill/cve-lookup
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 woohyun212/security-skill --skill cve-lookup
Clone the repo
git clone --depth 1 https://github.com/woohyun212/security-skill

Made for: Claude Code, Codex.

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 cve-lookup

README.md
[![agentmods](https://agentmods.dev/badge/skills/woohyun212/security-skill/cve-lookup/github.svg)](https://agentmods.dev/skills/woohyun212/security-skill/cve-lookup)
Your own site
<a href="https://agentmods.dev/skills/woohyun212/security-skill/cve-lookup"><img src="https://agentmods.dev/badge/skills/woohyun212/security-skill/cve-lookup/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 cve-lookup

Your own site · 80×15
<a href="https://agentmods.dev/skills/woohyun212/security-skill/cve-lookup"><img src="https://agentmods.dev/badge/skills/woohyun212/security-skill/cve-lookup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,117 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 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.00025 $0.02117
Opus 5 $0.00013 $0.01059
Sonnet 5 $0.00005 $0.00423
Haiku 4.5 $0.00003 $0.00212

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

Security

Grade B, and why

cve-lookup scanned grade B with 2 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 10d 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

sudo apt-get install -y curl jq

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- `curl` installed
cve-lookup/SKILL.md · 214 lines

How it starts

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

What this skill does

Queries CVE details via the NIST NVD (National Vulnerability Database) API v2. Parses CVSS v3/v2 scores and vectors, vulnerability descriptions, reference links, and affected product (CPE) lists, then outputs the results in a human-readable report format.

When to use

  • When you need to quickly understand the severity and attack vector of a specific CVE
  • When validating and prioritizing vulnerabilities found in scan results
  • When checking affected product versions to plan a patching strategy
  • When you need official CVE information for writing a vulnerability report

Prerequisites

  • curl installed
  • jq installed:
    sudo apt-get install -y curl jq
    
  • Internet access (NVD API requires no authentication, but rate limits apply)
  • API key optional (works without a key; key relaxes rate limits):

Inputs

Variable Required Description
SECSKILL_CVE_ID Required CVE ID to look up (e.g. CVE-2024-1234)
SECSKILL_OUTPUT_DIR Optional Directory to save results (default: ./output)
SECSKILL_NVD_API_KEY Optional NVD API key (relaxes rate limits)

Workflow

Step 1: Environment setup and CVE ID validation

export CVE_ID="${SECSKILL_CVE_ID:?Set the SECSKILL_CVE_ID environment variable (e.g. CVE-2024-1234)}"
export OUTDIR="${SECSKILL_OUTPUT_DIR:-./output}"
export NVD_KEY="${SECSKILL_NVD_API_KEY:-}"
mkdir -p "$OUTDIR"

# Validate CVE ID format
if ! echo "$CVE_ID" | grep -qE '^CVE-[0-9]{4}-[0-9]{4,}$'; then
  echo "[-] Invalid CVE ID format: $CVE_ID (expected format: CVE-YYYY-NNNNN)"
  exit 1
fi

echo "[*] Starting CVE lookup: $CVE_ID"
OUTFILE="$OUTDIR/cve_${CVE_ID}.txt"

Step 2: Query the NVD API v2

echo "[*] Querying NVD API..."
NVD_URL="https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=${CVE_ID}"
RAW_JSON="$OUTDIR/cve_raw_${CVE_ID}.json"

# Set API key header
API_HEADER=""
[ -n "$NVD_KEY" ] && API_HEADER="-H apiKey:${NVD_KEY}"

HTTP_CODE=$(curl -s -o "$RAW_JSON" -w "%{http_code}" \
  --max-time 30 \
  --retry 3 \
  --retry-delay 6 \
  $API_HEADER \
  "$NVD_URL")

if [ "$HTTP_CODE" = "404" ]; then
  echo "[-] CVE not found: $CVE_ID"
  exit 1
elif [ "$HTTP_CODE" != "200" ]; then
  echo "[-] NVD API error (HTTP $HTTP_CODE)"
  exit 1
fi

TOTAL=$(jq '.totalResults' "$RAW_JSON" 2>/dev/null)
if [ "$TOTAL" = "0" ] || [ -z "$TOTAL" ]; then
  echo "[-] No data found for $CVE_ID"
  exit 1
fi
echo "[+] CVE data received successfully"

Read the full file on GitHub · 214 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. 10d ago First seen · 214 lines · 25 tokens per session scan B 582bd5ca8f84

Subscribe to this mod's changes

cve-lookup is a skill published in the GitHub repository woohyun212/security-skill (21 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 2,117 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens