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/cross-pollinate)<a href="https://agentmods.dev/commands/byamb4/find-cve-agent/cross-pollinate"><img src="https://agentmods.dev/badge/commands/byamb4/find-cve-agent/cross-pollinate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/byamb4/find-cve-agent/cross-pollinate"><img src="https://agentmods.dev/badge/commands/byamb4/find-cve-agent/cross-pollinate.svg" alt="Reviewed on agentmods" width="80" 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.01039 |
| Opus 5 | $0.00016 | $0.00519 |
| Sonnet 5 | $0.00007 | $0.00208 |
| Haiku 4.5 | $0.00003 | $0.00104 |
Grade C, and why
cross-pollinate scanned grade C 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 9d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf /tmp/cross-pollinate-check How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cross-pollinate
Take a confirmed vulnerability pattern from the current finding and systematically search for the same pattern in similar packages.
Why Cross-Pollinate?
When you find a vulnerability in one package, similar packages often have the same bug. A ReDoS in one CSV parser likely exists in other CSV parsers. A path traversal in one archive library likely exists in other archive libraries.
This is the highest-ROI research strategy: one bug class, many CVEs.
Process
Step 1: Extract the Pattern
From the current confirmed finding, identify:
PATTERN EXTRACTION
Vulnerability class: <e.g., ReDoS, path traversal, prototype pollution>
Root cause pattern: <e.g., "regex with nested quantifiers on user input">
Code signature: <e.g., "new RegExp(userInput)" or "path.join(base, userInput)">
Grep pattern: <regex that would find this pattern in other codebases>
Package category: <e.g., CSV parsers, archive extractors, template engines>
Step 2: Find Similar Packages
Search for packages in the same category:
# npm search for similar packages
npm search "<category keyword>" --long | head -30
# GitHub search
gh search repos "<category>" --language javascript --stars 500..15000 --sort stars --limit 20
# Check which alternatives exist
# (often listed in the package's README as "alternatives" or "see also")
Step 3: Filter Candidates
For each similar package:
- Check REGISTRY.md -- skip if already investigated
- Check download count -- skip if <100K/week
- Check if it handles the same input type
- Quick grep for the vulnerable pattern:
# Clone minimally and search
git clone --depth 1 <repo-url> /tmp/cross-pollinate-check
grep -rn "<pattern>" /tmp/cross-pollinate-check/src/ /tmp/cross-pollinate-check/lib/
rm -rf /tmp/cross-pollinate-check
Step 4: Rank by Likelihood
Score each candidate:
| Factor | Score |
|---|---|
| Same language as original finding | +2 |
| Same input format (CSV, XML, etc.) | +3 |
| Grep pattern found in source | +5 |
| No existing CVEs for this vuln class | +3 |
| >500K weekly downloads | +2 |
| Active maintenance | +1 |
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.
- 9d ago First seen · 124 lines · 33 tokens per session scan C 7c855d9e0eda
cross-pollinate 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 1,039 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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.
check-dev
Type-check a Z specification with fuzz.
adr-supersede
Create a new ADR that supersedes an existing one.