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.
git clone --depth 1 https://github.com/ByamB4/find-cve-agentWrote 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.
[](https://agentmods.dev/commands/byamb4/find-cve-agent/registry)<a href="https://agentmods.dev/commands/byamb4/find-cve-agent/registry"><img src="https://agentmods.dev/badge/commands/byamb4/find-cve-agent/registry.svg" alt="Measured on agentmods" height="20"></a>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.00033 | $0.00548 |
| Opus 5 | $0.00016 | $0.00274 |
| Sonnet 5 | $0.00007 | $0.00110 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
registry 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/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
Check if a specific package has been investigated:
- Search REGISTRY.md for the package name
- Query OSV.dev for existing CVEs
- Report status: IN_PROGRESS / SUBMITTED / FALSE_POSITIVE / SKIP / DUPLICATE / CLEAN
/registry list
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
Manually add an entry to the registry. Prompts for required fields based on the section.
/registry move
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.
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.
- 8d ago First seen · 91 lines · 33 tokens per session scan A 926c5b6420ab
registry is a command published in the GitHub repository ByamB4/find-cve-agent (48 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 548 once invoked, about $0.0002 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-30.
Other commands, from other repositories
learn
Force claude-smart to extract learnings from this session now.
init
Install the formatters this repository needs, with every command visible before it runs.
brand-generate
Generate an on-brand document from a saved Brand Profile.
genshijin-compress
A command for safely shortening Markdown or text files into the genshijin style.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
audit-plugin
Audit plugin skills, commands, and agents for structure, size, and naming issues.