A command that checks whether the current project phase has met its completion rules before work moves on. It verifies scope, stored evidence, and whether findings are supported by that evidence.

Use it at a project checkpoint to validate a selected phase, rerun evidence checks, and stop advancement when required checks fail.

It prevents incomplete, out-of-scope, tampered, or unsupported work from being treated as finished.

engage.gate — Command for Claude Code by hypnguyen1209

Install

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.

Clone the repo

git clone --depth 1 https://github.com/hypnguyen1209/offensive-claude

agentmods

npx agentmods add commands/hypnguyen1209/offensive-claude/engage.gate

Made for: Claude Code.

Or install offensive-claude, the plugin that ships this one along with the rest of its 30 skills, 18 commands, 8 agents, 1 hook.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/hypnguyen1209/offensive-claude/engage.gate/github.svg)](https://agentmods.dev/commands/hypnguyen1209/offensive-claude/engage.gate)

Your own site

<a href="https://agentmods.dev/commands/hypnguyen1209/offensive-claude/engage.gate"><img src="https://agentmods.dev/badge/commands/hypnguyen1209/offensive-claude/engage.gate/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/hypnguyen1209/offensive-claude/engage.gate"><img src="https://agentmods.dev/badge/commands/hypnguyen1209/offensive-claude/engage.gate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 996 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00009	$0.00996
Opus 5	$0.00005	$0.00498
Sonnet 5	$0.00002	$0.00199
Haiku 4.5	$0.00001	$0.00100

Measured 9d ago against content hash e8bbd2636a73, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

engage.gate 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.

commands/engage.gate.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/engage.gate

Validates that the current phase meets all completion criteria before advancing to the next phase.

Usage

/engage.gate [--phase <phase-number>]

If no phase specified, validates the current active phase.

Validation Checks

Automated Enforcement (run these, don't just eyeball)

These executable checks back the gate — a phase cannot pass if they fail:

# Scope is enforced, not promised: every in-scope target must classify in-scope,
# and the scope file itself must be valid.
python skills/coding-mastery/scripts/_lib/scope_guard.py check <target> \
    --scope .engage/scope/scope.json

# Evidence must be re-verifiable: re-hash every captured artifact before trusting a citation.
# Exit 1 if any item is FAILED/UNVERIFIED (tampered, missing, or never hashed).
python skills/vulnerability-analysis/scripts/evidence_kit.py verify \
    --store .engage/evidence/evidence.json

# Findings must be grounded in evidence and survive per-class kill-signals.
# --evidence-store makes any [EVD-XXX] a finding cites have to EXIST and be VERIFIED, else REJECTED.
# --strict makes hedge / uncited lint on a CONFIRMED finding also fail the gate.
# Exit 1 if any finding is REJECTED (ungrounded / false-positive / dangling-or-unverified citation).
python skills/vulnerability-analysis/scripts/validate_findings.py \
    --findings .engage/exploit/findings.json --evidence .engage/evidence \
    --evidence-store .engage/evidence/evidence.json --strict

A finding only passes the gate if validate_findings.py tiers it CONFIRMED (or a documented CHAIN-REQUIRED). POSSIBLE/REJECTED findings do not advance. No finding advances past the exploit gate while it cites UNVERIFIED evidence — run evidence_kit.py verify first. See skills/references/finding-validation-runtime.md and finding-evidence-standards.md.

Artifact Validation

All required template files are populated
No placeholder text remains (e.g., "[TODO]", "[FILL IN]")
Required sections contain substantive content

Read the full file on GitHub · 125 lines

Changes

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 · 125 lines · 9 tokens per session scan A e8bbd2636a73

Subscribe to this mod's changes

engage.gate is a command published in the GitHub repository hypnguyen1209/offensive-claude (357 stars, last pushed 22d ago), licensed MIT. It adds 9 tokens to every session and 996 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.

Claude Code Project management claude-code-skills exploit-development offensive-security redteam

engage.gate