engage.exploit

engage.exploit is a command for coding agents from hypnguyen1209/offensive-claude. It costs 12 tokens per session (1,400 once invoked), scanned A, original, MIT.

A command for the exploitation phase of an authorized security engagement. It verifies access, examines the target, and guides actions such as privilege escalation, data collection, or movement to other systems when allowed by scope.

In plain words
What is it for?
Checking gained access, identifying privileges and security controls, gathering system and network information, and carrying out approved exploitation steps.
Why use it?
It provides a structured way to confirm that access is real and pursue the engagement's stated objectives.

Command

Part of the offensive-claude plugin — 30 skills, 18 commands, 8 agents, 1 hook 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 commands/hypnguyen1209/offensive-claude/engage.exploit
Clone the repo
git clone --depth 1 https://github.com/hypnguyen1209/offensive-claude

Or install offensive-claude, the plugin that ships this one along with the rest of its 30 skills, 18 commands, 8 agents, 1 hook.

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 engage.exploit

README.md
[![agentmods](https://agentmods.dev/badge/commands/hypnguyen1209/offensive-claude/engage.exploit.svg)](https://agentmods.dev/commands/hypnguyen1209/offensive-claude/engage.exploit)
Your own site
<a href="https://agentmods.dev/commands/hypnguyen1209/offensive-claude/engage.exploit"><img src="https://agentmods.dev/badge/commands/hypnguyen1209/offensive-claude/engage.exploit.svg" alt="Measured on agentmods" height="20"></a>
Per session 12 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,400 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.1 $0.00012 $0.01400
Opus 5 $0.00006 $0.00700
Sonnet 5 $0.00002 $0.00280
Haiku 4.5 $0.00001 $0.00140

Measured 5d ago against content hash 08eb113576a1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

engage.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 5d 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.

Asks for rootlowPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

Found: CVE-2021-3156 (sudo heap overflow)

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

commands/engage.exploit.md · 197 lines

How it starts

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

/engage.exploit

Executes Phase 4 (Exploitation) of the engagement workflow.

Usage

/engage.exploit [--target <host>] [--technique <technique-id>]

Options:

  • --target: Specify target host or application
  • --technique: Specify MITRE ATT&CK technique ID

Process

1. Load Template

Loads exploit/exploit-plan.md template.

2. Exploitation Planning

Reviews delivery outcome and plans exploitation:

  • What access was gained? (shell, web shell, credential, etc.)
  • What is the current privilege level?
  • What are the exploitation objectives? (per scope document)

3. Exploitation Execution

Guides through exploitation chain:

Initial Access Verification:

  • Confirm access is functional
  • Identify current user/privileges
  • Identify target OS and environment
  • Check for security controls (AV/EDR, logging, monitoring)

Situational Awareness:

  • Enumerate system information
  • Identify network configuration
  • Locate sensitive data or credentials
  • Map internal network (if applicable)

Objective Achievement: Based on engagement scope, execute:

  • Data exfiltration (if authorized)
  • Privilege escalation (if needed)
  • Lateral movement (if needed)
  • Persistence establishment (if needed)

Evidence Collection: For each successful exploitation step:

  • Capture screenshot or command output
  • Document exploitation technique
  • Record MITRE ATT&CK technique ID
  • Note any indicators of compromise (IOCs)

4. Finding Documentation

For each successful exploit, creates finding record in exploit/findings/:

Finding Template (finding-<id>.md):

# Finding: [Title]

**Severity**: Critical / High / Medium / Low
**CWE**: CWE-XXX
**CVE**: CVE-YYYY-NNNN (if applicable)
**MITRE ATT&CK**: T1XXX

## Description
[Detailed vulnerability description]

## Exploitation
[Step-by-step exploitation procedure]

## Impact
[Business impact and risk]

## Evidence
- Screenshot: evidence/screenshots/finding-<id>-01.png
- Output log: evidence/logs/finding-<id>.log

## Remediation
[Specific remediation guidance]

## References
[CVE links, vendor advisories, etc.]

Read the full file on GitHub · 197 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. 5d ago First seen · 197 lines · 12 tokens per session scan A 08eb113576a1

Subscribe to this mod's changes

engage.exploit is a command published in the GitHub repository hypnguyen1209/offensive-claude (354 stars, last pushed 19d ago), licensed MIT. It adds 12 tokens to every session and 1,400 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.