scan-cves

A command that scans a website or reconnaissance results for known security vulnerabilities, called CVEs. CVEs are public records describing specific software security flaws; the command can also run a separate scan for the Log4j flaw when available.

In plain words
What is it for?
Use it to scan a host, a recon directory, or selected URLs, optionally limit results by year, and save findings and Log4j output for manual confirmation.
Why use it?
It narrows testing to known vulnerabilities instead of running a broad scan, making it useful for focused follow-up checks.

Command

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 commands/awarexone/agentic-bug-hunter/scan-cves
Clone the repo
git clone --depth 1 https://github.com/Awarexone/Agentic-Bug-Hunter
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 402 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.00402
Opus 5 $0.00000 $0.00201
Sonnet 5 $0.00000 $0.00080
Haiku 4.5 $0.00000 $0.00040

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

Security

Grade A, and why

scan-cves 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 3d 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.

commands/scan-cves.md · 43 lines

What it actually says

/scan-cves

Targeted nuclei scan of the cve/ template directory plus optional log4j-scan.

Usage

/scan-cves https://target.com
/scan-cves --recon recon/target.com
/scan-cves --year 2024 recon/target.com/live/urls.txt

Why a separate command

/recon already runs a broad nuclei phase across every severity — this command narrows to known CVEs only, which:

  • Cuts the runtime by an order of magnitude (high/critical CVE templates only).
  • Surfaces signals that pay even on dormant programs (CVE-2021-44228 still hits on legacy enterprise hosts).
  • Lets you re-scan one or two URLs without rerunning the full pipeline.

Set NUCLEI_NO_UPDATE=1 to skip the template update on each run when iterating quickly.

Output

findings/cve/<timestamp>/:

  • nuclei_cve.jsonl — one finding per line (template ID, host, severity)
  • log4j.txt — optional log4j-scan output when the scanner is installed

After a hit

  1. Confirm the version manually (don't trust the template — show the response).
  2. Check program scope and reward table; many CVEs are explicitly out-of-scope if the program already disclosed them or is mid-patch.
  3. Provide a non-destructive PoC: a single request that proves the version is vulnerable, not a working exploit chain.
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. 3d ago First seen · 43 lines · 0 tokens per session scan A c62bc3d8c086

Subscribe to this mod's changes

scan-cves is a command published in the GitHub repository Awarexone/Agentic-Bug-Hunter (4,651 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 402 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-30.

Related

Other commands, from other repositories

recon

Run full recon pipeline on a target — subdomain enum (Chaos API + subfinder), live host discovery (dnsx + httpx), URL crawl (katana + waybackurls + gau), gf pattern classification, nuclei scan. Outputs to recon/ / directory. Usage: /recon target.com.

elementalsouls/Claude-BugHunter · 65 tokens

hunt

Active vulnerability hunting. Two-track dispatcher — asks Red Team vs WAPT, hands off to hunt-dispatch skill and sibling commands. Usage: /hunt target.com | /hunt .target.com | /hunt targets.txt [--vuln-class X] [--source-code P] [--chrome].

elementalsouls/Claude-BugHunter · 63 tokens

token-scan

Meme coin and token security scan — checks for rug pull vectors (hidden mint, honeypot, fee manipulation, LP lock bypass, authority retention, bonding curve exploits, fake renounce, sandwich amplification). Manual 8-class grep audit (with an optional automated scanner if present). Usage: /token-scan [--chain solana].

elementalsouls/Claude-BugHunter · 79 tokens

autopilot

Run autonomous hunt loop on a target — scope check → recon → rank surface → hunt → validate → report with configurable checkpoints. Usage: /autopilot target.com [--paranoid|--normal|--yolo].

elementalsouls/Claude-BugHunter · 49 tokens

triage

Quick 7-Question Gate triage on a finding before writing a report. Kills N/A submissions before they happen. Faster than /validate — for quick go/no-go decisions. Usage: /triage.

elementalsouls/Claude-BugHunter · 45 tokens

validate

Validate a finding — runs 7-Question Gate + 4-gate checklist. Kills weak findings before report writing. Prevents N/A submissions that hurt validity ratio. Usage: /validate.

elementalsouls/Claude-BugHunter · 41 tokens