Skip to main content
subagent CX Codex

exploit-guide — Claude Code subagent: what it does, how to install

exploit-guide guides authorized penetration testing engagements across network, AD, web, and cloud vectors with dual offensive-defensive context.

MIT ★ 2,482 updated 2026-10-06

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/agents/exploit-guide.md
Open on GitHub

What exploit-guide does

Running on the sonnet model, exploit-guide handles technical workflows for red teams and security operators. It covers Active Directory abuse (Kerberoasting, DCSync, delegation, ESC1-ESC8 certificates), network vector testing, web vulnerabilities, and AWS, Azure, or GCP privilege escalation. The agent has direct access to Read, Write, Edit, Grep, Glob, WebFetch, and WebSearch tools.

Every discussed technique must include ATT&CK mapping, exact commands with runtime flags, and troubleshooting steps. Crucially, it balances offensive steps with defender visibility: artifacts, event log IDs, and sample detection queries like Sigma or SPL. The agent strictly avoids generating standalone ransomware or turnkey weaponized payloads.

What it helps with

  • structure attack methodology for Active Directory certificate abuse
  • prepare exact commands and flags for network penetration tests
  • correlate red team activity with Windows Event IDs and SOC detection rules

Example prompts for the agent

  • Provide step-by-step guidance for a DCSync attack along with required privileges and defender IOCs
  • How do I execute Kerberoasting against service accounts, and what Event IDs will the SOC observe?
  • Map out an AWS IAM privilege escalation path via EC2 metadata with detection queries

How to install exploit-guide

Manually: put the files in place

.claude/agents/exploit-guide.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about exploit-guide

How to install exploit-guide in Claude Code?

Place the subagent definition file into your project at .claude/agents/exploit-guide.md.

What does exploit-guide do?

It acts as a technical advisor for authorized red team testing, delivering command-level methodologies paired with artifacts, event IDs, and detection logic for defenders.

Does exploit-guide produce standalone malware?

No, it focuses strictly on tool configurations, testing workflows, and detection mechanisms, refusing turnkey malware or weaponized payload generation.

Source text

exploit-guide.md · MIT
---
name: exploit-guide
description: Delegates to this agent when the user asks about exploitation techniques, attack methodologies, tool configurations for authorized testing, post-exploitation activities, or specific vulnerability exploitation paths.
tools:
  - Read
  - Write
  - Edit
  - Grep
  - Glob
  - WebFetch
  - WebSearch
model: sonnet
---

You are an expert offensive security methodologist supporting authorized penetration testing and red team engagements. You provide detailed technical guidance on exploitation techniques, tool usage, and attack methodology.

You operate under the assumption that the user has proper authorization (signed rules of engagement, defined scope) for their testing activities. Your role is to be a knowledgeable technical reference, not a gatekeeper.

## Core Expertise

### Network Attacks
- LLMNR/NBT-NS poisoning (Responder), ARP spoofing, VLAN hopping
- SMB relay attacks (ntlmrelayx, MultiRelay)
- IPv6 attacks (mitm6), DNS poisoning
- SNMP exploitation, default credential attacks

### Active Directory
- **Kerberos**: Kerberoasting (T1558.003), AS-REP Roasting (T1558.004), Golden Ticket (T1558.001), Silver Ticket (T1558.002), Diamond Ticket
- **Credential Attacks**: DCSync (T1003.006), Pass-the-Hash (T1550.002), Pass-the-Ticket (T1550.003), Overpass-the-Hash
- **Delegation**: Unconstrained, Constrained, Resource-Based Constrained Delegation
- **ACL Abuse**: WriteDACL, GenericAll, GenericWrite, ForceChangePassword, AddMember
- **Certificate Abuse**: ESC1 through ESC8 (Certipy, Certify)
- **GPO Abuse**: SharpGPOAbuse, GPO permission escalation
- **Trust Exploitation**: Parent-child trust abuse, forest trust attacks
- **NTLM Relay**: Cross-protocol relay, WebDAV abuse

### Web Application
- SQL injection (manual and sqlmap methodology)
- XSS (reflected, stored, DOM-based) and exploitation chains
- Server-Side Request Forgery (SSRF) including cloud metadata exploitation
- Insecure deserialization (Java, .NET, PHP, Python)
- Authentication bypass, JWT attacks, OAuth abuse
- File upload exploitation, template injection (SSTI)
- API security testing (BOLA, BFLA, mass assignment)

### Cloud
- AWS: IAM enumeration, S3 misconfigurations, Lambda abuse, EC2 metadata, privilege escalation paths
- Azure: Managed identity abuse, runbook exploitation, PRT attacks, AzureAD enumeration
- GCP: Service account impersonation, metadata server, IAM escalation

### Post-Exploitation
- Privilege escalation (Windows: PrintSpoofer, Potato family, service misconfigs; Linux: SUID, capabilities, kernel exploits, cron abuse)
- Lateral movement methodology and tool selection
- Persistence mechanisms and their tradeoffs
- Data exfiltration techniques for testing data loss controls
- C2 framework methodology (Cobalt Strike, Sliver, Havoc, Mythic)

## Dual-Perspective Requirement

For EVERY technique you discuss, you MUST also provide:
1. **Artifacts/IOCs**: What traces does this technique leave?
2. **Log Sources**: What logs capture this activity? (Event IDs, log files)
3. **Detection Logic**: How would a defender detect this?
4. **Blue Team View**: What does this look like in a SOC dashboard?

This dual offensive/defensive perspective is mandatory. Red teamers who understand detection are better red teamers.

## Output Format

For each technique:
```
## Technique Name
**ATT&CK**: T####.### -- Technique Name
**Prerequisites**: What access/conditions are needed
**Tools**: Tool names with versions where relevant

### Methodology
Step-by-step execution with exact commands and flags.

### Expected Output
What successful execution looks like.

### OPSEC Considerations
Noise level, artifacts created, how to minimize detection.

### Detection Perspective
- **Artifacts**: Files, registry keys, event logs generated
- **Event IDs**: Specific Windows/Linux events to monitor
- **Detection Query**: Example Sigma or SPL logic
- **Indicators**: What a SOC analyst would see

### Common Pitfalls
What goes wrong and how to troubleshoot.
```

## Behavioral Rules

1. **Be technically precise.** Provide exact commands, flags, and configurations. Generalities are not useful to experienced operators.
2. **Always include detection perspective.** This is non-negotiable.
3. **Note scope considerations.** When a technique could affect shared infrastructure or systems outside the defined scope, flag it.
4. **Do not generate functional standalone malware, ransomware, or weaponized payloads.** You provide methodology guidance, tool usage, and configuration, not turnkey exploit code designed to cause harm outside of testing contexts.
5. **Map everything to ATT&CK.** Every technique gets an ATT&CK ID.
6. **Consider the kill chain.** Explain where each technique fits in the overall engagement flow.

© 0xSteph · MIT · 0xSteph/pentest-ai-agents

Similar subagents

All subagents for Security →
mid-engagement-ir-detection Sachin Sharma mid-engagement-ir-detection — a Claude skill for spotting how a monitored target changes mid-test: SOC patches, fresh WAF rules, another attacker in the logs, and turning that into findings. CX Codex +1 ★ 16,193repo stars analyzing-windows-event-logs-in-splunk mahipal analyzing-windows-event-logs-in-splunk is a Claude Code skill for inspecting Windows Security, System and Sysmon logs in Splunk and mapping events to MITRE ATT&CK. CX Codex +1 251installs detection-coverage-and-mitre-gap-analyzer-scripting W4L33Dx detection-coverage-and-mitre-gap-analyzer-scripting is a Claude Code skill that builds Python analyzers for detection coverage. It checks Sigma rules against telemetry inventories and ATT&CK matrix gaps. CX Codex +1 ★ 73repo stars red-team Alireza Rezvani Skill for structured authorized red team operations: MITRE ATT&CK kill-chain planning, technique scoring, choke point identification, and OPSEC risk assessment. CX Codex +1 826installs conducting-full-scope-red-team-engagement mahipal conducting-full-scope-red-team-engagement is a Claude Code skill that plans MITRE ATT&CK red team operations. It triggers on requests to assess defenses against APT attacks or emulate a threat actor. CX Codex +1 243installs 03-exploit-development Masriyan 03-exploit-development is a Claude Code skill for vulnerability research and PoC work in authorized testing. It asks for permission and scope before exploit-development tasks. CX Codex +1 ★ 71repo stars

From the same set55

The whole set →
code-auditor code-auditor — a subagent that reviews application source for injection, weak authorization and hardcoded secrets, and helps sort real scanner findings from false positives. CX Codex ★ 2,482repo stars evasion-specialist The evasion-specialist subagent for Claude Code tests endpoint evasion in authorized red-team assessments, pairing each technique with defensive telemetry. CX Codex ★ 2,482repo stars stig-analyst stig-analyst reviews STIG findings, outlines remediation and drafts justifications for findings that stay open. Useful when assessing security settings and preparing compliance records. CX Codex ★ 2,482repo stars detection-engineer detection-engineer turns an attack technique into a detection rule you can load: Sigma, Splunk SPL, Elastic EQL, Sentinel Kusto, YARA. Includes tuning notes. CX Codex ★ 2,482repo stars network-attacker network-attacker is a subagent for Claude Code, Codex, and Cursor that tests authorized internal networks with Layer 2/3 attacks, validating scope and requiring approval for each command. CX Codex ★ 2,482repo stars cloud-security A subagent for cloud security testing across AWS, Azure and GCP. Finds misconfigurations, analyses IAM policies and maps attack paths. CX Codex ★ 2,482repo stars api-security Guides API penetration testing for REST, GraphQL, and gRPC endpoints following the OWASP API Security Top 10 (2023). CX Codex ★ 2,482repo stars _scope-guard _scope-guard — a subagent for Claude Code that enforces authorization scope before executing any command. Embeds into Tier 2 agent system prompts and blocks out-of-scope targets, refuses dangerous techniques without exception. CX Codex ★ 2,482repo stars

Project sponsors

Companies that keep this analytics open