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 commands/byamb4/find-cve-agent/reportgit 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/report)<a href="https://agentmods.dev/commands/byamb4/find-cve-agent/report"><img src="https://agentmods.dev/badge/commands/byamb4/find-cve-agent/report.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.01124 |
| Opus 5 | $0.00016 | $0.00562 |
| Sonnet 5 | $0.00007 | $0.00225 |
| Haiku 4.5 | $0.00003 | $0.00112 |
Grade A, and why
report scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "https://hackerone.com/directory/programs" | grep -i "<project>" How it starts
The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/report
Generate a professional disclosure report for a confirmed vulnerability finding.
Prerequisites
- Finding must be CONFIRMED by the Validator (verdict.md exists with CONFIRMED)
- PoC must be working (poc_*.py exits 0)
- CVSS score must be calculated
Process
Step 1: Gather Finding Details
Read from the target directory:
targets/<repo>/findings.mdfor technical detailstargets/<repo>/verdict.mdfor confirmationtargets/<repo>/poc_<vuln_type>.pyfor the PoC headertargets/<repo>/brief.mdfor project info
Step 2: Determine Disclosure Channel
Check in priority order:
-
HackerOne: Search for the project
curl -s "https://hackerone.com/directory/programs" | grep -i "<project>"If found -> use HackerOne format
-
GitHub Security Advisory: Check if repo has advisories enabled
gh api "repos/<owner>/<repo>" --jq '.has_security_policy // false'If true -> use GHSA format
-
SECURITY.md: Check for security contact
gh api "repos/<owner>/<repo>/contents/SECURITY.md" --jq '.content' | base64 -d 2>/dev/nullIf exists -> use email format
-
Package maintainer email: Check package registry
npm view <package> maintainers --json 2>/dev/nullIf found -> use email format
-
GitHub Issue: Last resort
Step 3: Generate Report
GitHub Security Advisory Format
## Summary
[Vulnerability Type] in [package-name] [component] allows [impact description].
## Details
**Affected package**: [name]
**Affected versions**: [version range, e.g., "<= 3.2.1"]
**Patched version**: None (0-day)
### Root Cause
[Technical description of the vulnerability. Include the file path and line number.
Explain why the current code is vulnerable and what an attacker can do.]
### Attack Vector
[Step-by-step description of how an attacker would exploit this.]
1. [Step 1]
2. [Step 2]
3. [Step 3]
### Impact
[What an attacker can achieve. Be specific: read files, execute commands, etc.]
## Proof of Concept
[PoC code or steps to reproduce]
## Severity
**CVSS**: [vector string] = [score] [severity]
**CWE**: [CWE-XXX] ([name])
## Suggested Fix
[Specific recommendation for how to fix the vulnerability.
Include code examples if possible.]
## Timeline
- [Date]: Vulnerability discovered
- [Date]: Report submitted via [channel]
- [Date + 90 days]: Planned public disclosure (if no response)
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.
- 5d ago First seen · 197 lines · 33 tokens per session scan A 0fd433f6a75d
report is a command published in the GitHub repository ByamB4/find-cve-agent (47 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 1,124 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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
Markdown・テキストファイルを原始人形式へ安全圧縮.
wp-polylang
Translate an existing WordPress site into a second language using Polylang.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.