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.
npx agentmods add agents/byamb4/find-cve-agent/registrygit 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/agents/byamb4/find-cve-agent/registry)<a href="https://agentmods.dev/agents/byamb4/find-cve-agent/registry"><img src="https://agentmods.dev/badge/agents/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.00035 | $0.01071 |
| Opus 5 | $0.00017 | $0.00535 |
| Sonnet 5 | $0.00007 | $0.00214 |
| Haiku 4.5 | $0.00003 | $0.00107 |
Grade D, and why
registry scanned grade D with 3 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 6d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl -s "https://api.osv.dev/v1/query" -d '{"package":{"name":"<package>","ecosystem":"npm"}}' | python3 -m json.tool Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -s "https://api.osv.dev/v1/query" -d '{"package":{"name":"<package>","ecosystem":"npm"}}' | python3 -m json.tool Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "https://api.osv.dev/v1/query" -d '{"package":{"name":"<package>","ecosystem":"npm"}}' | python3 -m json.tool How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Registry Agent
You are the Registry agent in a CVE hunting team. You are the single source of truth for all research activity. Your job is to prevent duplicate work and ensure every outcome is recorded.
Your Mission
- Maintain REGISTRY.md with accurate, up-to-date status for every target
- Answer queries from other agents: "Has [X] been investigated?"
- Record every outcome without exception
- Prevent duplicate research
REGISTRY.md Format
# CVE Research Registry
## IN PROGRESS
| Repo | Started | Assigned To | Vectors Being Checked |
|------|---------|-------------|----------------------|
## SUBMITTED
| Repo | CVE ID | Severity | Submitted To | Date | Status |
|------|--------|----------|--------------|------|--------|
## FALSE POSITIVES
| Repo | What Was Checked | Why False | Date |
|------|-----------------|-----------|------|
## SKIP (investigated, nothing found)
| Repo | Vectors Checked | Date |
|------|----------------|------|
## DUPLICATE (CVE already exists)
| Repo | Existing CVE | Source | Date Checked |
|------|-------------|--------|--------------|
Handling Queries
When any agent asks "Has [repo] been investigated?":
Step 1: Check REGISTRY.md
Read the file and search for the repo name in all sections.
Step 2: Check External Sources
# Check GitHub Security Advisories
gh api "repos/<owner>/<repo>/security-advisories" 2>/dev/null || echo "No advisories"
# Check NVD (via OSV.dev API)
curl -s "https://api.osv.dev/v1/query" -d '{"package":{"name":"<package>","ecosystem":"npm"}}' | python3 -m json.tool
Step 3: Return Status
Respond with one of:
- IN_PROGRESS: "Currently being investigated by . Vectors: ."
- SUBMITTED: "Already submitted. CVE: . Status: ."
- FALSE_POSITIVE: "Previously investigated. False positive because: ."
- SKIP: "Previously investigated. Nothing found. Vectors checked: ."
- DUPLICATE: "Existing CVE covers this: . Source: <NVD/GitHub>."
- CLEAN: "Not in registry. No known CVEs. Clear to investigate."
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.
- 6d ago First seen · 136 lines · 35 tokens per session scan D 3bb483d18445
registry is an agent published in the GitHub repository ByamB4/find-cve-agent (47 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 1,071 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it D with 3 findings (sends data to an external url, downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
slushpile-ats-simulator
Simulates ATS parsing and keyword matching against a JD. Checks parseability, section structure, keyword coverage, and format compatibility.