/recon
Find targets in a category. Usage: /recon <category>. Examples: /recon csv-parsers, /recon template-engines, /recon archive-libs.
$ npx -y skills add ByamB4/find-cve-agent --agent claude-codeShips with find-cve-agent. Installing the plugin gets this command.
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/recon
Context preview
What this command does when you run it.
Find targets in a category. Usage: /recon <category>. Examples: /recon csv-parsers, /recon template-engines, /recon archive-libs.
Command definition
recon.mdname: recon
description: "Find targets in a category. Usage: /recon <category>. Examples: /recon csv-parsers, /recon template-engines, /recon archive-libs."
/recon <category>
Find promising targets in a specific package category for CVE hunting.
Process
Step 1: Search Package Registries
Based on the category argument, search for relevant packages:
# npm search
npm search "$ARGUMENTS" --long 2>/dev/null | head -20
# GitHub search (adjust language and keywords per category)
gh search repos "$ARGUMENTS" --language javascript --stars 500..15000 --sort stars --limit 20
gh search repos "$ARGUMENTS" --language python --stars 500..15000 --sort stars --limit 20
gh search repos "$ARGUMENTS" --language go --stars 500..15000 --sort stars --limit 20
Step 2: Filter Candidates
For each result, quickly evaluate: 1. Stars: 500-15K? (skip if outside range) 2. Last commit: within 6 months? (skip if abandoned) 3. Already in REGISTRY.md? (skip if yes) 4. More than 10 existing CVEs? (skip if over-audited)
Step 3: Deep Evaluation (Top 5)
For the top 5 candidates, gather detailed info:
# Download counts
curl -s "https://api.npmjs.org/downloads/point/last-week/<package>"
# Repo details
gh repo view <owner>/<repo> --json stargazerCount,pushedAt,description,licenseInfo
# Security advisories count
gh api "repos/<owner>/<repo>/security-advisories" 2>/dev/null | python3 -c "import sys,json; data=json.load(sys.stdin); print(len(data))" 2>/dev/null || echo "0"
Step 4: Rank and Present
Present candidates to the Director ranked by promise:
RECON RESULTS: <category>
#1. <package-name>
Stars: <count> | Downloads: <count>/week | Language: <lang>
Attack surface: <brief>
Existing CVEs: <count>
Top vector: <most promising>
Rating: HIGH / MEDIUM / LOW
#2. <package-name>
...
#3. <package-name>
...Step 5: Propose Top Pick
Recommend the best candidate to the Director:
Proposed target: <package-name>
Reason: <why this is the best candidate>
Approve? (I'll create the full brief on approval)
Category Keywords
| Category Argument | Search Terms | |---|---| | csv-parsers | csv parse, csv parser, csv reader | | xml-parsers | xml parse, sax parser, xml reader | | template-engines | template engine, mustache, handlebars, nunjucks | | archive-libs | zip extract, tar extract, archive, decompress | | validators | validate, schema validator, json schema | | file-handlers | file upload, multipart, file process | | serializers | serialize, deep clone, deep merge, marshal | | url-parsers | url parse, uri, query string | | image-libs | image process, sharp, jimp, image resize | | pdf-libs | pdf parse, pdf generate, pdf reader | | markdown | markdown parse, markdown render, markdown-it | | yaml | yaml parse, yaml load | | auth-libs | jwt, oauth, session, authentication | | crypto | encrypt, decrypt, hash, cipher | | cli-tools | cli, command line, terminal, exec |
Read more
name: recon description: "Find targets in a category. Usage: /recon <category>. Examples: /recon csv-parsers, /recon template-engines, /recon archive-libs."
/recon <category>
Find promising targets in a specific package category for CVE hunting.
Process
Step 1: Search Package Registries
Based on the category argument, search for relevant packages:
# npm search npm search "$ARGUMENTS" --long 2>/dev/null | head -20 # GitHub search (adjust language and keywords per category) gh search repos "$ARGUMENTS" --language javascript --stars 500..15000 --sort stars --limit 20 gh search repos "$ARGUMENTS" --language python --stars 500..15000 --sort stars --limit 20 gh search repos "$ARGUMENTS" --language go --stars 500..15000 --sort stars --limit 20
Step 2: Filter Candidates
For each result, quickly evaluate: 1. Stars: 500-15K? (skip if outside range) 2. Last commit: within 6 months? (skip if abandoned) 3. Already in REGISTRY.md? (skip if yes) 4. More than 10 existing CVEs? (skip if over-audited)
Step 3: Deep Evaluation (Top 5)
For the top 5 candidates, gather detailed info:
# Download counts curl -s "https://api.npmjs.org/downloads/point/last-week/<package>" # Repo details gh repo view <owner>/<repo> --json stargazerCount,pushedAt,description,licenseInfo # Security advisories count gh api "repos/<owner>/<repo>/security-advisories" 2>/dev/null | python3 -c "import sys,json; data=json.load(sys.stdin); print(len(data))" 2>/dev/null || echo "0"
Step 4: Rank and Present
Present candidates to the Director ranked by promise:
RECON RESULTS: <category>
#1. <package-name>
Stars: <count> | Downloads: <count>/week | Language: <lang>
Attack surface: <brief>
Existing CVEs: <count>
Top vector: <most promising>
Rating: HIGH / MEDIUM / LOW
#2. <package-name>
...
#3. <package-name>
...Step 5: Propose Top Pick
Recommend the best candidate to the Director:
Proposed target: <package-name> Reason: <why this is the best candidate> Approve? (I'll create the full brief on approval)
Category Keywords
| Category Argument | Search Terms | |---|---| | csv-parsers | csv parse, csv parser, csv reader | | xml-parsers | xml parse, sax parser, xml reader | | template-engines | template engine, mustache, handlebars, nunjucks | | archive-libs | zip extract, tar extract, archive, decompress | | validators | validate, schema validator, json schema | | file-handlers | file upload, multipart, file process | | serializers | serialize, deep clone, deep merge, marshal | | url-parsers | url parse, uri, query string | | image-libs | image process, sharp, jimp, image resize | | pdf-libs | pdf parse, pdf generate, pdf reader | | markdown | markdown parse, markdown render, markdown-it | | yaml | yaml parse, yaml load | | auth-libs | jwt, oauth, session, authentication | | crypto | encrypt, decrypt, hash, cipher | | cli-tools | cli, command line, terminal, exec |
Open Source CVE Hunting Harness for Claude Code A Claude Code plugin that systematically finds real CVEs in open source packages through coordinated multi-agent security research.
Repo: ByamB4/find-cve-agent
Other commands on find-cve-agent.
- /check-nvd
Query NVD and OSV.dev for existing CVEs. Usage: /check-nvd <package-name>. Shows CVE count, severity breakdown, and recent fixes.
Open command - /cross-pollinate
Take a confirmed vulnerability pattern and find the same bug in similar packages. Usage: /cross-pollinate (run after confirming a finding).
Open command - /fp-check
Run the 6-gate false positive elimination process on the current finding. Usage: /fp-check (run from a target directory with findings).
Open command - /hunt
Full CVE hunting pipeline. Usage: /hunt <package-name>. Orchestrates all agents: registry check, clone, code review, PoC build, validation, and report generation.
Open command - /registry
Query or update the research registry. Usage: /registry [query]. Examples: /registry stats, /registry check lodash, /registry list in-progress.
Open command - /report
Generate a disclosure report from the current finding. Auto-detects the best submission channel. Usage: /report (run from target directory with confirmed finding).
Open command

