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.
npx agentmods add commands/hypnguyen1209/offensive-claude/engage.exploitgit clone --depth 1 https://github.com/hypnguyen1209/offensive-claudeWrote 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.
[](https://agentmods.dev/commands/hypnguyen1209/offensive-claude/engage.exploit)<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>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.
| Model | Per session | Once 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 |
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.
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.]
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.
- 5d ago First seen · 197 lines · 12 tokens per session scan A 08eb113576a1
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.
Other commands, from other repositories
discover
Run a full product discovery cycle — from outcome definition through opportunity mapping, prioritisation, and experiment design. Use when the team isn't sure what to build next, or before writing a PRD for a complex feature space.
resume
Resume a previous session. Reads recent session logs, open tasks, and last decisions — gives Claude full context without re-explaining the project.
voice-compliance
Voice/telephony compliance check — invokes voice-ai-reviewer to produce TM-voice-{slug}.md with TCPA, STIR/SHAKEN, state recording-consent, EU AI Act Art. 50, and synth-voice deepfake-law gaps.
claude-tracker
List and browse your saved Claude Code sessions with status (running/inactive/VS Code).
update-workflow
Regenerate an existing custom workflow's shortcut command wiring from the current swarm template.
save
Save this conversation as a new or existing reusable context.