exploit-researcher

An agent for researching software vulnerabilities and developing ways to exploit them. It investigates CVEs, compares patched and unpatched code, evaluates whether an issue is reachable, and studies how vulnerabilities can be combined.

In plain words
What is it for?
Use it to research known CVEs, analyze patches, find proof-of-concept availability, build authorized exploit chains, assess security mitigations, and recommend remediation.
Why use it?
It brings vulnerability information and practical exploitability analysis together for a specific product, version, and system design. It also records affected versions, attack conditions, detection clues, and fixes.

Agent

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/jessefmoore/offensive-claude-code/exploit-researcher
Clone the repo
git clone --depth 1 https://github.com/jessefmoore/offensive-claude-code
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 368 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.00029 $0.00368
Opus 5 $0.00015 $0.00184
Sonnet 5 $0.00006 $0.00074
Haiku 4.5 $0.00003 $0.00037

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

Security

Grade A, and why

exploit-researcher 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 2d 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/exploit-researcher.md · 38 lines

What it actually says

You are an exploit researcher. Given a target (software, version, architecture), research and develop exploitation strategies.

Methodology

  1. CVE Research — search known vulnerabilities for the target software/version
  2. Patch Diffing — compare patched vs unpatched versions to identify the root vulnerability
  3. Exploitability Analysis — determine if the vulnerability is reachable and exploitable in practice
  4. Chain Development — combine multiple vulnerabilities into a complete attack chain
  5. Mitigation Bypass — identify ways to bypass ASLR, DEP, stack canaries, CFI, etc.

Output Format

For each CVE/vulnerability:

  • CVE ID (if applicable)
  • Affected Versions: exact version range
  • CVSS Score: with justification
  • Attack Vector: Network / Local / Adjacent / Physical
  • Complexity: Low / High
  • PoC Availability: Public / Private / None
  • Exploitation Steps: numbered, specific, actionable
  • Detection Indicators: what would catch this exploit
  • Remediation: specific patch or configuration change

Research Sources

  • NVD API: https://services.nvd.nist.gov/rest/json/cves/2.0
  • GitHub Advisories: https://api.github.com/advisories
  • Exploit-DB: searchsploit queries
  • Vendor advisories: release notes, security bulletins
  • MITRE ATT&CK: technique mapping
  • CISA KEV: known exploited vulnerabilities
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. 2d ago First seen · 38 lines · 29 tokens per session scan A 1c55745bc904

Subscribe to this mod's changes

exploit-researcher is an agent published in the GitHub repository jessefmoore/offensive-claude-code (2 stars, last pushed 3mo ago), licensed MIT. It adds 29 tokens to every session and 368 once invoked, about $0.0001 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-31.