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.
git 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.c2)<a href="https://agentmods.dev/commands/hypnguyen1209/offensive-claude/engage.c2"><img src="https://agentmods.dev/badge/commands/hypnguyen1209/offensive-claude/engage.c2/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.
<a href="https://agentmods.dev/commands/hypnguyen1209/offensive-claude/engage.c2"><img src="https://agentmods.dev/badge/commands/hypnguyen1209/offensive-claude/engage.c2.svg" alt="Reviewed on agentmods" width="80" 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.00010 | $0.01293 |
| Opus 5 | $0.00005 | $0.00647 |
| Sonnet 5 | $0.00002 | $0.00259 |
| Haiku 4.5 | $0.00001 | $0.00129 |
Grade A, and why
engage.c2 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/engage.c2
Executes Phase 6 (Command and Control) of the engagement workflow.
Usage
/engage.c2 [--framework <framework>] [--protocol <protocol>]
Options:
--framework: C2 framework (cobalt-strike, sliver, mythic, havoc, custom)--protocol: Communication protocol (https, dns, smb, tcp)
Process
1. Load Templates
Loads:
c2/c2-infrastructure.md— C2 architecture and configurationc2/opsec-checklist.md— Operational security checklist
2. C2 Framework Selection
Based on engagement requirements:
Framework Options:
- Cobalt Strike: Industry standard, Malleable C2 profiles, BOF support
- Sliver: Open-source, cross-platform implants, multiplayer
- Mythic: Modular agents, web UI, extensive logging
- Havoc: Modern framework, evasion-focused, Demon agent
- Custom: Purpose-built for specific engagement needs
Protocol Selection:
- HTTPS: Standard web traffic (port 443), high blend-in
- DNS: Low-and-slow exfiltration, bypasses most firewalls
- SMB: Internal lateral movement, named pipe communication
- TCP: Direct connection, fastest but most detectable
3. Infrastructure Setup
Documents in c2-infrastructure.md:
Architecture Design:
- C2 server location and hardening
- Redirector configuration (Apache/Nginx/CDN)
- Domain categorization and aging
- SSL/TLS certificate setup
Redirector Configuration:
- Frontend redirector (filters non-C2 traffic)
- Backend C2 server (hidden from target)
- Domain fronting setup (if applicable)
- CDN-based redirection (Cloudflare, AWS CloudFront)
Communication Profile:
- Beacon interval and jitter
- HTTP headers and URI patterns
- User-Agent strings
- Payload encryption (AES, ChaCha20)
- Data encoding (base64, custom)
Infrastructure Hardening:
- Firewall rules (only accept beacon traffic)
- SSH access controls
- Logging configuration
- Kill switch mechanism
4. Beacon Verification
After setup:
- Confirm beacon callback from target
- Verify C2 command execution
- Test data exfiltration channel
- Validate encryption is functioning
- Check beacon stability over time
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.
- 9d ago First seen · 181 lines · 10 tokens per session scan A ce8d1d59aa88
engage.c2 is a command published in the GitHub repository hypnguyen1209/offensive-claude (357 stars, last pushed 23d ago), licensed MIT. It adds 10 tokens to every session and 1,293 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-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.
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 recent Claude Code sessions with live status.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.
esp-harden
Harden and inspect ESP32 firmware for field failures, crashes, memory, and security.
replication-package
Scaffold or audit a social-science replication package at a target directory, and audit the manuscript and its archived research objects against FAIR principles.