engagement-startup

engagement-startup is a skill for Claude Code from MingyiSecLab/Mingyi-Atlas. It costs 23 tokens per session (687 once invoked), scanned A, original, Apache-2.0.

A mandatory first-step procedure for starting or resuming a red-team security engagement. It checks the workspace for existing engagements, then initializes a new one or summarizes an existing engagement before continuing.

In plain words
What is it for?
Use it at the start of every session to list engagements, choose whether to resume or create one, review planning and findings files, and identify the next objective.
Why use it?
It prevents the agent from losing track of earlier work or beginning without knowing the target, scope, current phase, and pending objectives.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents.

Good fit Use it at the start of every session to list engagements, choose whether to resume or create one, review planning and findings files, and identify the next objective.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mingyiseclab/mingyi-atlas/engagement-startup
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.

Any agent
npx skills add MingyiSecLab/Mingyi-Atlas --skill engagement-startup
Clone the repo
git clone --depth 1 https://github.com/MingyiSecLab/Mingyi-Atlas

Made for: Claude Code.

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.

agentmods badge for engagement-startup

README.md
[![agentmods](https://agentmods.dev/badge/skills/mingyiseclab/mingyi-atlas/engagement-startup/github.svg)](https://agentmods.dev/skills/mingyiseclab/mingyi-atlas/engagement-startup)
Your own site
<a href="https://agentmods.dev/skills/mingyiseclab/mingyi-atlas/engagement-startup"><img src="https://agentmods.dev/badge/skills/mingyiseclab/mingyi-atlas/engagement-startup/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.

agentmods 80×15 button for engagement-startup

Your own site · 80×15
<a href="https://agentmods.dev/skills/mingyiseclab/mingyi-atlas/engagement-startup"><img src="https://agentmods.dev/badge/skills/mingyiseclab/mingyi-atlas/engagement-startup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 687 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.00687
Opus 5 $0.00012 $0.00344
Sonnet 5 $0.00005 $0.00137
Haiku 4.5 $0.00002 $0.00069

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

Security

Grade A, and why

engagement-startup 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 11d 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.

src/skills/standard/atlas/engagement-startup/SKILL.md · 87 lines

How it starts

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

Engagement Startup Procedure

Execute this procedure on every session start, before any other action.

Step 1: Discover Existing Engagements

bash(command="ls -1 /workspace/ 2>/dev/null || echo '[empty]'")

Step 2: Present Options to Operator

If engagements exist

Present a numbered list and ask:

Existing engagements found:
  1. acme-external-2026
  2. internal-audit-q1

Options:
  [number] Resume an engagement
  [new]    Start a new engagement

Which would you like?

If no engagements exist

No existing engagements found. Let's set up a new one.
What is the target or scope for this engagement?

Step 3A: Resume Existing Engagement

  1. Read planning documents:
    read_file("<engagement>/plan/roe.json")
    read_file("<engagement>/plan/conops.json")
    read_file("<engagement>/plan/deconfliction.json")
    read_file("<engagement>/plan/opplan.json")
    read relevant files under "<engagement>/findings/"
    
  2. Summarize progress to the operator:
    • Objectives completed / total
    • Current phase (recon / exploit / post-exploit)
    • Last completed objective and key findings
    • Next pending objective
  3. Ask: "Continue from where we left off?"
  4. Begin the Ralph execution loop

Step 3B: New Engagement (docs already created by Soundwave)

Soundwave has already interviewed the operator and created the engagement documents (RoE, CONOPS, Deconfliction Plan) before the orchestrator was activated. The workspace and planning documents already exist.

  1. Verify documents exist:
    bash(command="ls plan/roe.json plan/conops.json plan/deconfliction.json")
    
    If any are missing, delegate to soundwave to regenerate:
    task("soundwave", "Engagement workspace: /workspace/. Regenerate missing planning documents.")
    
  2. Check C2 Infrastructure:
    bash(command="nc -z c2-sliver 31337 2>/dev/null && echo 'C2_REACHABLE' || echo 'C2_UNREACHABLE'")
    
    • If C2_REACHABLE → C2 framework is Sliver (server: c2-sliver, gRPC port 31337). Include this in ALL sub-agent delegations.
    • If C2_UNREACHABLE → C2 server is not available, skip C2-dependent objectives
    • IMPORTANT: The C2 framework is always Sliver regardless of the engagement name. Do NOT assume Metasploit from engagement names containing "msf".
  3. Begin the Ralph execution loop (Phase 1: read CONOPS → build OPPLAN)

Read the full file on GitHub · 87 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.

  1. 11d ago First seen · 87 lines · 23 tokens per session scan A 410d4f81babc

Subscribe to this mod's changes

engagement-startup is a skill published in the GitHub repository MingyiSecLab/Mingyi-Atlas (11 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 687 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.