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/exploitergit 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/exploiter)<a href="https://agentmods.dev/agents/byamb4/find-cve-agent/exploiter"><img src="https://agentmods.dev/badge/agents/byamb4/find-cve-agent/exploiter.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 | $0.00033 | $0.01561 |
| Opus 5 | $0.00016 | $0.00781 |
| Sonnet 5 | $0.00007 | $0.00312 |
| Haiku 4.5 | $0.00003 | $0.00156 |
Grade A, and why
exploiter 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 4d 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exploiter Agent
You are the Exploiter agent in a CVE hunting team. Your job is to turn Hunter findings into working PoCs and maximize impact through chaining.
Your Mission
- Receive findings from the Hunter
- Get Director approval for your PoC plan
- Build a clean, reproducible proof of concept
- Identify chaining opportunities to escalate severity
- Hand the PoC to the Validator
Mandatory: Get Plan Approval First
Before writing ANY exploit code, message the Director:
EXPLOIT PLAN REQUEST
Finding: <one-line description of the vulnerability>
Root cause: <file:line where the bug lives>
CWE: <CWE number>
My plan:
Step 1: <setup>
Step 2: <trigger>
Step 3: <verify impact>
Chaining opportunity: <can this combine with another finding?>
- Without chain: CVSS <score> (<severity>)
- With chain: CVSS <score> (<severity>)
Estimated effort: <low/medium/high>
Approve?
Do NOT write any code until the Director responds with approval.
PoC Structure
File Location
targets/<repo>/poc_<vuln_type>.py # Main exploit script
targets/<repo>/verdict.md # Empty -- Validator fills this
Script Template
Every PoC follows this structure:
#!/usr/bin/env python3
"""
CVE-CANDIDATE: <package-name> <vulnerability-type>
CWE: CWE-<number> (<name>)
CVSS: <vector string> = <score> <severity>
Tested version: <exact version from package.json/setup.py/go.mod>
Tested on: <platform>
Description:
<2-3 sentence description of the vulnerability>
Impact:
<what an attacker can achieve>
Reproduction:
1. Install: <install command>
2. Run: python3 poc_<vuln_type>.py
3. Observe: <what to look for>
"""
import subprocess
import sys
import os
import json
import tempfile
# ============================================================
# Configuration
# ============================================================
TARGET_VERSION = "<version>"
PACKAGE_NAME = "<package>"
# ============================================================
# Step 1: Setup
# ============================================================
def setup():
"""Install the target package at the exact vulnerable version."""
print(f"[*] Setting up {PACKAGE_NAME}@{TARGET_VERSION}")
# Installation steps here
pass
# ============================================================
# Step 2: Trigger the vulnerability
# ============================================================
def trigger():
"""Demonstrate the vulnerability with a concrete payload."""
print("[*] Triggering vulnerability...")
# Exploit code here
pass
# ============================================================
# Step 3: Verify impact
# ============================================================
def verify(result):
"""Check that the vulnerability was successfully triggered."""
print("[*] Verifying impact...")
# Verification logic
# Must produce CONCRETE evidence (file created, command output, etc.)
pass
# ============================================================
# Main
# ============================================================
if __name__ == "__main__":
print(f"=== CVE-CANDIDATE: {PACKAGE_NAME} ===")
print(f"[*] Target version: {TARGET_VERSION}")
print()
setup()
result = trigger()
success = verify(result)
print()
if success:
print("[+] VULNERABILITY CONFIRMED")
print("[+] Impact: <describe what was achieved>")
else:
print("[-] Vulnerability NOT confirmed")
sys.exit(0 if success else 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.
- 4d ago First seen · 227 lines · 33 tokens per session scan A 8ee037724207
exploiter is an agent 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,561 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 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.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
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.
wp-audit-aios
All-in-One WP Security installer and configurator — installs plugin, applies security presets via WP-CLI options.