What is engage.install?

An installation procedure for establishing persistence during a security engagement. Persistence means keeping access to a computer after a restart or after the original entry point changes.

Use it to plan persistence through services, scheduled tasks, startup settings, registry entries, authorized keys, or other listed mechanisms, along with cleanup procedures.

It organizes environment checks and method selection, including detection risk and available access points.

engage.install — Command for Claude Code by hypnguyen1209

Install

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.

Clone the repo

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

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.install/github.svg)](https://agentmods.dev/commands/hypnguyen1209/offensive-claude/engage.install)

Your own site

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

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

When invoked 1,112 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.00010	$0.01112
Opus 5	$0.00005	$0.00556
Sonnet 5	$0.00002	$0.00222
Haiku 4.5	$0.00001	$0.00111

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

Security

Grade A, and why

engage.install 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.install.md · 183 lines

How it starts

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

/engage.install

Executes Phase 5 (Installation/Persistence) of the engagement workflow.

Usage

/engage.install [--method <persistence-method>]

Options:

--method: Specify persistence method (service, cron, startup, registry, implant)

Process

1. Load Templates

Loads:

install/persistence-mechanism.md — Persistence design and implementation
install/cleanup-plan.md — Cleanup and removal procedures

2. Environment Assessment

Before installing persistence:

Identify current access level and user context
Enumerate installed security controls (AV, EDR, HIDS)
Identify available persistence locations
Assess detection risk for each method

3. Persistence Method Selection

Choose method based on target environment and OPSEC requirements:

Linux Methods:

Cron job (user or system level)
Systemd service or timer
Bashrc/profile modification
SSH authorized_keys
Kernel module (requires root)
LD_PRELOAD hijacking

Windows Methods:

Registry run keys
Scheduled task
Windows service
WMI event subscription
DLL hijacking/side-loading
COM object hijacking
Startup folder

Cross-Platform Methods:

Web shell
Implant with auto-reconnect
Backdoored application binary

4. Implementation

Documents in persistence-mechanism.md:

Persistence Details:

Method selected and justification
Installation location (path, registry key, etc.)
Execution trigger (boot, login, scheduled, event-based)
Payload stored/dropped
Expected behavior after installation

Stealth Considerations:

File timestamps (timestomp if needed)
Log suppression or cleanup
AV/EDR evasion for persistence mechanism
Naming conventions (blend with legitimate entries)
Digital signatures (if applicable)

5. Verification

After installation:

Verify persistence survives reboot/relogin
Confirm callback to C2
Test failover and recovery
Monitor for security alerts

6. Cleanup Plan

Populates cleanup-plan.md with:

Cleanup Steps (ordered):

Exact commands to remove persistence
Files to delete
Registry keys to remove
Services to stop and delete
Logs to review for artifacts

Read the full file on GitHub · 183 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 · 183 lines · 10 tokens per session scan A d850f9fe70c1

Subscribe to this mod's changes

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

Claude Code Security claude-code-skills exploit-development offensive-security redteam

engage.install