exploiter

exploiter is an agent for coding agents from ByamB4/find-cve-agent. It costs 33 tokens per session (1,561 once invoked), scanned A, original, Apache-2.0.

A security agent that turns a reported software vulnerability into a reproducible proof of concept, meaning a small demonstration that the flaw works. It also checks whether multiple flaws can be combined to increase their effect.

In plain words
What is it for?
Use it to build approved exploit demonstrations, test vulnerability triggers, document their effects, and assess possible vulnerability chains.
Why use it?
It gives security teams a concrete way to verify a suspected bug and understand its possible impact before handing it to a validator.

Agent

Part of the find-cve-agent plugin — 21 skills, 7 commands, 5 agents shipped together

Install

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.

agentmods
npx agentmods add agents/byamb4/find-cve-agent/exploiter
Clone the repo
git clone --depth 1 https://github.com/ByamB4/find-cve-agent

Or install find-cve-agent, the plugin that ships this one along with the rest of its 21 skills, 7 commands, 5 agents.

Wrote 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.

agentmods badge for exploiter

README.md
[![agentmods](https://agentmods.dev/badge/agents/byamb4/find-cve-agent/exploiter.svg)](https://agentmods.dev/agents/byamb4/find-cve-agent/exploiter)
Your own site
<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>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,561 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 4d ago against content hash 8ee037724207, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

agents/exploiter.md · 227 lines

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

  1. Receive findings from the Hunter
  2. Get Director approval for your PoC plan
  3. Build a clean, reproducible proof of concept
  4. Identify chaining opportunities to escalate severity
  5. 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)

Read the full file on GitHub · 227 lines

Changes

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.

  1. 4d ago First seen · 227 lines · 33 tokens per session scan A 8ee037724207

Subscribe to this mod's changes

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.