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.status)<a href="https://agentmods.dev/commands/hypnguyen1209/offensive-claude/engage.status"><img src="https://agentmods.dev/badge/commands/hypnguyen1209/offensive-claude/engage.status/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.status"><img src="https://agentmods.dev/badge/commands/hypnguyen1209/offensive-claude/engage.status.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.00007 | $0.00339 |
| Opus 5 | $0.00003 | $0.00169 |
| Sonnet 5 | $0.00001 | $0.00068 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
engage.status 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 10d 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.
What it actually says
/engage.status
Displays the current state of the active engagement workflow.
Usage
/engage.status
Output
Shows:
- Engagement Info: Client name, workflow type, start date
- Current Phase: Active phase name and number (0-8)
- Completed Phases: List of phases that passed gate validation
- Gate Status: Current phase gate validation status (pass/fail/pending)
- Findings Count: Total findings across all phases
- Evidence Collected: Count of screenshots, pcaps, logs
- Suggested Next Action: Recommended next command to run
Phase Status Indicators
- ✓ Phase completed and gate passed
- → Current active phase
- ○ Phase not yet started
- ✗ Phase gate validation failed
Example Output
Engagement: ACME Corp Web Application Pentest
Workflow: web-app
Started: 2026-05-28
Pipeline Status:
✓ Phase 0: Scope Definition
✓ Phase 1: Reconnaissance
→ Phase 2: Weaponization (IN PROGRESS)
○ Phase 3: Delivery
○ Phase 4: Exploitation
Current Phase Gate: PENDING
Findings: 12 total (3 critical, 5 high, 4 medium)
Evidence: 47 screenshots, 8 pcaps, 23 logs
Suggested Next Action: Complete payload configuration, then run /engage.gate
Notes
Run this command frequently to track progress and ensure you're following the workflow sequence.
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.
- 10d ago First seen · 55 lines · 7 tokens per session scan A 807d6a9ee7df
engage.status is a command published in the GitHub repository hypnguyen1209/offensive-claude (357 stars, last pushed 23d ago), licensed MIT. It adds 7 tokens to every session and 339 once invoked, about $0.0000 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.