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.actions)<a href="https://agentmods.dev/commands/hypnguyen1209/offensive-claude/engage.actions"><img src="https://agentmods.dev/badge/commands/hypnguyen1209/offensive-claude/engage.actions/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.actions"><img src="https://agentmods.dev/badge/commands/hypnguyen1209/offensive-claude/engage.actions.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.00011 | $0.01630 |
| Opus 5 | $0.00005 | $0.00815 |
| Sonnet 5 | $0.00002 | $0.00326 |
| Haiku 4.5 | $0.00001 | $0.00163 |
Grade A, and why
engage.actions 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.
How it starts
The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/engage.actions
Executes Phase 7 (Actions on Objectives) of the engagement workflow.
Usage
/engage.actions [--objective <objective-id>]
Options:
--objective: Execute a specific objective from the scope document
Process
1. Load Templates
Loads:
actions/objectives.md— Engagement objectives trackeractions/collection-plan.md— Data collection and handling plan
Action gate (non-negotiable): every outward action in this phase passes through
skills/coding-mastery/scripts/_lib/action_guard.py— out-of-scope targets are blocked, mutating/ destructive operations require explicit approval (unless the ROE setsallow_mutating), and the per-host circuit breaker halts activity against a failing target. Destructive actions (data deletion, account changes, persistence on systems not authorized for it) are blocked outright.
2. Objective Review
Retrieves engagement objectives from Phase 0 scope document:
- Lists all defined objectives
- Identifies which objectives are already achieved (from Phase 4)
- Prioritizes remaining objectives by impact and feasibility
- Determines what additional access or movement is needed
3. Objective Execution
For each remaining objective:
Lateral Movement (if needed):
- Identify reachable network segments
- Enumerate accessible hosts and services
- Discover credentials or tokens for movement
- Move to target systems via authorized techniques
- Document each pivot point
Privilege Escalation (if needed):
- Identify current privilege level on target system
- Enumerate escalation vectors
- Execute escalation technique
- Document pre/post privilege level
Data Discovery and Collection (if authorized):
- Locate target data per engagement scope
- Document data locations and access method
- Collect representative samples only (per ROE)
- Handle data per engagement data handling policy
- Never exfiltrate production customer data without explicit authorization
Domain Dominance (AD engagements):
- Enumerate Active Directory structure
- Identify domain admin paths
- Execute Kerberos attacks (if authorized)
- Achieve domain admin (if objective)
- Document trust relationships
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 · 217 lines · 11 tokens per session scan A 61405b0b7b48
engage.actions is a command published in the GitHub repository hypnguyen1209/offensive-claude (357 stars, last pushed 23d ago), licensed MIT. It adds 11 tokens to every session and 1,630 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
save
Save current session. Writes a session log with what was done, decisions made, and what's pending. Optional: commit & push.
skillify
Capture a repeating pattern as a reusable skill. Run when you notice the same 5+ steps appearing 3+ times across sessions or agents. Produces a skills/ /SKILL.md file.
url
Print the tlive web terminal/dashboard link + QR code.
claude-tracker
List recent Claude Code sessions with live status.
quote
Capture a notable phrase or excerpt from the current session with optional tags. Stored in tracker.db and searchable via /quote-search.
claude-tracker-search
Search across all your Claude sessions for specific keywords.