SkillAgentSearch skills...

engagement-flow

Use when starting, planning, or running a multi-phase pentest or red-team engagement — to sequence the Cyber Kill Chain phases with quality gates instead of jumping straight to exploitation

Install / Use

npx skills add hypnguyen1209/offensive-claude --skill engagement-flow

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

81/100

Category

Security

Supported Platforms

Universal

Tags

Our assessment of engagement-flow

engagement-flow scores 81/100 on our quality scale, 985th of 1,097 Security skills we index.

Its SKILL.md is 3.1 KB long, split into 6 sections with 1 code example: a solid amount of guidance for an agent.

It has 377 GitHub stars, a meaningful sign that others use it.

Substance
26/30
Structure
15/20
Description
15/15
Adoption
11/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so engagement-flow is actively maintained.
  • Our last check on 2026-11-08 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-26. Automated pattern scan on 2026-10-26. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

engagement-flow compared with similar skills

All 4 of these similar skills score higher than engagement-flow; compare them before choosing.

SkillScoreStarsUpdatedFormat
engagement-flow (this skill)by hypnguyen1209813772mo agoSKILL.md
algorithmic-artby anthropics100177.9k58d agoSKILL.md
pptxby anthropics100177.9k58d agoSKILL.md
prospectingby coreyhaines3110060.1k8d agoSKILL.md
ad-creativeby coreyhaines3110060.1k8d agoSKILL.md

Frequently asked questions

How do I install engagement-flow?
Run npx skills add hypnguyen1209/offensive-claude --skill engagement-flow. The install tabs above show the steps for each supported agent.
Which AI agents does engagement-flow work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is engagement-flow safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is engagement-flow still maintained?
The repository was last updated about 2 months ago, so engagement-flow is actively maintained.

name: engagement-flow description: Use when starting, planning, or running a multi-phase pentest or red-team engagement — to sequence the Cyber Kill Chain phases with quality gates instead of jumping straight to exploitation

Engagement Flow

Overview

A pentest/red-team engagement is a phased pipeline with gates, not a pile of techniques run ad hoc. This skill sequences the 9-phase Lockheed Martin Cyber Kill Chain and routes each phase to its commands, domain skills, and discipline checks. It is the offensive analog of brainstorming → writing-plans → executing-plans: scope the work, plan it, then execute phase by phase.

Don't jump to exploitation. Earlier phases earn the access that later phases need, and each gate keeps quality high before you advance.

The pipeline

digraph killchain {
    rankdir=LR;
    scope -> recon -> weaponize -> deliver -> exploit -> install -> c2 -> actions -> report;
    scope [label="0 SCOPE"]; recon [label="1 RECON"]; weaponize [label="2 WEAPONIZE"];
    deliver [label="3 DELIVER"]; exploit [label="4 EXPLOIT"]; install [label="5 INSTALL"];
    c2 [label="6 C2"]; actions [label="7 ACTIONS"]; report [label="8 REPORT"];
}

Each transition requires a gate (/engage.gate): required artifacts present, findings carry CWE+CVSS+ATT&CK+evidence, and the automated checks pass. Gate FAIL → fix the gap before advancing.

How to run it

  1. Pick the workflow preset for the engagement type (web-app, network, red-team, cloud, mobile, ad-domain, bug-bounty) and drive phases with the /engage.* commands.
  2. Phase 0 (scope): emit .engage/scope/scope.json. REQUIRED: scope-discipline.
  3. Phases 1-7: before any target interaction → scope-discipline; before any outward action → opsec-discipline; invoke the matching domain skill for the technique.
  4. Recall prior intel: at recon/weaponize, /engage.memory recall to start from what worked.
  5. Findings: REQUIRED: finding-discipline — nothing is [CONFIRMED] without proof.
  6. Phase 8 (report): record confirmed findings to engagement-memory; generate the report.
  7. Optional autopilot: engine/engine.py runs the phases under a budget/loop/trace with --resume (/engage.pickup); offensive actions stay operator-gated.

Red Flags — STOP, back up a phase

  • "Let me just start exploiting" (no scope.json / no recon → back to phase 0/1)
  • "Skip the gate, I'll document later" (gates exist so the report is complete and findings are real)
  • "Recon is done, I didn't check prior intel" (run /engage.memory recall)

Quick reference

| Phase | Command | Discipline / tooling | |-------|---------|----------------------| | Scope | /engage.scope | scope-discipline → scope.json | | Recon | /engage.recon | scope-discipline; /engage.memory recall | | Exploit | /engage.exploit | opsec-discipline; finding-discipline | | Actions | /engage.actions | action_guard gate; opsec-discipline | | Report | /engage.report | finding-discipline; record to memory | | Gate / resume | /engage.gate, /engage.pickup | automated checks; engine trace |

Related Skills

View on GitHub
GitHub Stars377
CategorySecurity
Updated2mo ago
Forks65

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions