/registry
Query or update the research registry. Usage: /registry [query]. Examples: /registry stats, /registry check lodash, /registry list in-progress.
$ 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
/registry
Context preview
What this command does when you run it.
Query or update the research registry. Usage: /registry [query]. Examples: /registry stats, /registry check lodash, /registry list in-progress.
Command definition
registry.mdname: registry
description: "Query or update the research registry. Usage: /registry [query]. Examples: /registry stats, /registry check lodash, /registry list in-progress."
/registry [query]
Query or display information from the CVE research registry.
Subcommands
/registry (no arguments)
Display a summary of the registry:
REGISTRY SUMMARY
In Progress: <count> targets
Submitted: <count> findings (<count> with CVE IDs)
False Positives: <count>
Skipped: <count>
Duplicates: <count>
Total investigated: <sum>
Success rate: <submitted / total investigated>%
False positive rate: <false positives / total investigated>%
/registry stats
Detailed statistics:
REGISTRY STATISTICS
By severity:
CRITICAL: <count>
HIGH: <count>
MEDIUM: <count>
LOW: <count>
By channel:
GitHub Advisory: <count>
HackerOne: <count>
Direct email: <count>
By status:
Assigned CVE: <count>
Awaiting triage: <count>
Rejected: <count>
By vulnerability type:
<type>: <count>
<type>: <count>
...
Recent activity (last 7 days):
<date> | <action> | <target>
...
/registry check <package>
Check if a specific package has been investigated:
1. Search REGISTRY.md for the package name 2. Query OSV.dev for existing CVEs 3. Report status: IN_PROGRESS / SUBMITTED / FALSE_POSITIVE / SKIP / DUPLICATE / CLEAN
/registry list <section>
List all entries in a specific section:
- `/registry list in-progress` - Show all targets currently being investigated
- `/registry list submitted` - Show all submitted findings
- `/registry list false-positives` - Show all false positives with reasons
- `/registry list skip` - Show all skipped targets
- `/registry list duplicate` - Show all duplicates with existing CVE IDs
/registry add <package> <section>
Manually add an entry to the registry. Prompts for required fields based on the section.
/registry move <package> <from-section> <to-section>
Move an entry between sections. Used when status changes (e.g., IN_PROGRESS -> SUBMITTED).
Implementation
Read REGISTRY.md, parse the markdown tables, and present the requested information. For updates, use the Edit tool to modify REGISTRY.md in place.
Read more
name: registry description: "Query or update the research registry. Usage: /registry [query]. Examples: /registry stats, /registry check lodash, /registry list in-progress."
/registry [query]
Query or display information from the CVE research registry.
Subcommands
/registry (no arguments)
Display a summary of the registry:
REGISTRY SUMMARY In Progress: <count> targets Submitted: <count> findings (<count> with CVE IDs) False Positives: <count> Skipped: <count> Duplicates: <count> Total investigated: <sum> Success rate: <submitted / total investigated>% False positive rate: <false positives / total investigated>%
/registry stats
Detailed statistics:
REGISTRY STATISTICS By severity: CRITICAL: <count> HIGH: <count> MEDIUM: <count> LOW: <count> By channel: GitHub Advisory: <count> HackerOne: <count> Direct email: <count> By status: Assigned CVE: <count> Awaiting triage: <count> Rejected: <count> By vulnerability type: <type>: <count> <type>: <count> ... Recent activity (last 7 days): <date> | <action> | <target> ...
/registry check <package>
Check if a specific package has been investigated:
1. Search REGISTRY.md for the package name 2. Query OSV.dev for existing CVEs 3. Report status: IN_PROGRESS / SUBMITTED / FALSE_POSITIVE / SKIP / DUPLICATE / CLEAN
/registry list <section>
List all entries in a specific section:
- `/registry list in-progress` - Show all targets currently being investigated
- `/registry list submitted` - Show all submitted findings
- `/registry list false-positives` - Show all false positives with reasons
- `/registry list skip` - Show all skipped targets
- `/registry list duplicate` - Show all duplicates with existing CVE IDs
/registry add <package> <section>
Manually add an entry to the registry. Prompts for required fields based on the section.
/registry move <package> <from-section> <to-section>
Move an entry between sections. Used when status changes (e.g., IN_PROGRESS -> SUBMITTED).
Implementation
Read REGISTRY.md, parse the markdown tables, and present the requested information. For updates, use the Edit tool to modify REGISTRY.md in place.
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 - /recon
Find targets in a category. Usage: /recon <category>. Examples: /recon csv-parsers, /recon template-engines, /recon archive-libs.
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