Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/hypnguyen1209/offensive-claudenpx agentmods add commands/hypnguyen1209/offensive-claude/engage.scopeWrote 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.scope)<a href="https://agentmods.dev/commands/hypnguyen1209/offensive-claude/engage.scope"><img src="https://agentmods.dev/badge/commands/hypnguyen1209/offensive-claude/engage.scope.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.00011 | $0.00749 |
| Opus 5 | $0.00005 | $0.00375 |
| Sonnet 5 | $0.00002 | $0.00150 |
| Haiku 4.5 | $0.00001 | $0.00075 |
Grade A, and why
engage.scope 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 8d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/engage.scope
Executes Phase 0 (Scope Definition) of the engagement workflow.
Usage
/engage.scope
Process
1. Load Template
Loads scope/scope-definition.md template with sections:
- Engagement Overview
- Target Information
- Rules of Engagement (ROE)
- Authorization
- Scope Boundaries (in-scope / out-of-scope)
- Emergency Contacts
- Timeline
2. Interactive Scope Definition
Works with you to populate:
Target Information:
- Primary targets (domains, IP ranges, applications)
- Target environment (production/staging/dev)
- Technology stack (if known)
Rules of Engagement:
- Allowed testing hours
- Prohibited actions (DoS, social engineering, physical access)
- Data handling requirements
- Notification procedures
Authorization:
- Authorization letter/email reference
- Authorized contact name and role
- Authorization scope and limitations
Scope Boundaries:
- Explicitly in-scope assets
- Explicitly out-of-scope assets (third-party services, shared infrastructure)
Emergency Contacts:
- Primary technical contact
- Security team contact
- Escalation contact
- After-hours contact
Timeline:
- Engagement start date
- Engagement end date
- Reporting deadline
3. Emit machine-readable scope (scope.json)
Translate the in-scope / out-of-scope boundaries into .engage/scope/scope.json following
templates/scope/scope.schema.json (see templates/scope/scope.example.json). This file is
the enforced boundary — every active script consults it via scope_guard.py, so "stay in
scope" stops being a promise and becomes a check.
mkdir -p .engage/scope
# ...write scope.json with engagement, authorization_ref, in_scope[], out_of_scope[], roe{}...
# Sanity-check it loads and that a known in-scope target classifies correctly:
python skills/coding-mastery/scripts/_lib/scope_guard.py check api.acme.com \
--scope .engage/scope/scope.json
Remember: *.acme.com matches sub-domains only — list the apex acme.com separately;
out_of_scope always wins.
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.
- 8d ago First seen · 123 lines · 11 tokens per session scan A b4828bfae0b7
engage.scope is a command published in the GitHub repository hypnguyen1209/offensive-claude (357 stars, last pushed 21d ago), licensed MIT. It adds 11 tokens to every session and 749 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.
fec-smell
Diagnose frontend code smells with evidence and candidate refactorings without changing business code.
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.