Skip to main content
skill CX Codex

coordination — Claude Code skill: pentest orchestration

coordination — a skill for coordinating agents in security testing workflows. Manages executor and validator spawning, holds engagement state in a single context, and avoids delegating thinking to sub-subagents.

MIT 198 installs ★ 632 updated 2026-07-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add transilienceai/communitytools --skill coordination -a claude-code
Open on GitHub

What coordination does

Coordination runs as a spawned subagent per target. It reads all accessible application code before any executor batch, writes attack-chain.md, and cycles through: think (write 3 hypotheses), test (spawn 1–2 executors), validate (fresh blind agent per candidate), update the chain. The workflow enforces a 30-experiment cap with mandatory skeptic checkpoints at experiments 5, 15, and 25. Validation is interleaved — each candidate is verified the moment it materializes. If a hypothesis fails three times on one goal, the skill triggers Creative Research and rereads all data with a fresh theory.

Roles (executor, skeptic, validator) stay isolated by context; each receives only what it needs. The final report outputs only validated findings in Transilience PDF format. The parent orchestrator must not run this workflow inline — if you execute P1–P5 in the main session, you skipped the spawn step and bookkeeping discipline silently breaks.

What it helps with

  • Orchestrate multiple agents without duplicating effort or losing state
  • Track hypotheses and test batches in a single context across batches
  • Validate findings using blind agents without leaking prior context
  • Escape a failing hypothesis after three attempts and switch to creative research
  • Generate a report containing only confirmed findings

Example prompts for the agent

  • Spawn coordination with attack-chain.md for each new target in an engagement
  • Write 3 hypotheses, tag one [wildcard], and pass the chain to executors
  • Validate each candidate on a fresh blind agent the moment it materializes

How to install coordination

1Skills CLI (Vercel)

npx skills add transilienceai/communitytools --skill coordination -a claude-code

2Manually: put the files in place

~/.claude/skills/coordination/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/coordination/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about coordination

How do I install coordination in Claude Code?

Run npx skills add transilienceai/communitytools --skill coordination -a claude-code, then open ~/.claude/skills/coordination/SKILL.md.

What does coordination do?

It manages the pentest workflow: reads source code, generates hypotheses, spawns executors and validators as separate agents, maintains an experiments ledger, and triggers Creative Research if a hypothesis fails three times on one goal.

Why can't coordination run inline in the parent orchestrator?

Because it holds engagement state and manages subagent spawning. Running it inline breaks the context discipline and silently disables bookkeeping.

Source text

SKILL.md · MIT
---
name: coordination
description: Pentest coordination — orchestrates executor and validator agents with context-controlled spawning. Entry point for all engagements.
---

# Coordination

Runs as a spawned subagent (one per target). Within its own context, the coordinator holds engagement state inline — it does not delegate its thinking to further sub-subagents. Thinks before every action.

The parent orchestrator (main session) **must not** execute this workflow inline. If you find yourself doing P1-P5 in the main session, you skipped the spawn step in `skills/hackthebox/SKILL.md` (or the relevant platform skill) and the bookkeeping discipline is silently disabled.

## Principle (Rule 0)

**Source code first.** Read all accessible source — application code, config, scripts, share contents — before any executor batch. Every answer is in the data you already have. Guessing without reading is the most common failure mode.

## Workflow

```
P0: Ingest scope
 ↓
P1: Recon + read source code → write attack-chain.md → run preflight-checklist
 ↓
┌→ P2: Think — read chain + experiments.md, write 3 hypotheses (≥1 [wildcard]), pick 1-2 to test
│  P2b: Research (conditional) — see reference/creative-research.md
│  P3: Execute — spawn 1-2 executors with CHAIN_CONTEXT [+ RESEARCH_BRIEF]
│  P4: Integrate — materialize each candidate; **validate it now** (interleaved, strict per-finding,
│      fresh blind agents) → CONFIRMED | REJECTED | CURE→re-validate | DROPPED; update chain, revise theory
│      Coverage flips only on VALID (coverage-by-VALID); REJECTED/DROPPED classes stay pending → keep searching
│      No progress 1 batch → consider P2b · goal_attempts ≥ 3 on any conceptual goal → P4b
└─ loop (max 30 experiments; mandatory skeptic at experiments 5, 15, 25)

P4b: Reset — re-read all recon + source + chain. Creative Research (mandatory). Fresh theory.
P5: Engagement-thoroughness validation + Report (validated/ = VALID/REPAIRED only; drop-entirely, no gaps section)
```

### Steps

1. **Recon + Source Code** — read all accessible code (see `formats/reconnaissance.md`). Run pre-flight checklist (`reference/preflight-checklist.md`).
2. **Think** — write 3 hypotheses to `attack-chain.md`, ≥1 tagged `[wildcard]`. Pick 1-2 to spawn.
3. **Test** — 1-2 executors per batch, integrate before next.
4. **Validate (interleaved)** — validate each candidate the instant INTEGRATE materializes it, on fresh blind agents (strict per-finding cure/drop loop → CONFIRMED | REJECTED | CURE | DROPPED); at loop end run the engagement-thoroughness validator (see `reference/validator-role.md`).
5. **Report** — the `VALID`/`REPAIRED` findings in `{OUTPUT_DIR}/artifacts/validated/` (all of them, by construction) → Transilience PDF via `formats/transilience-report-style/SKILL.md`.

## attack-chain.md

`{OUTPUT_DIR}/attack-chain.md`. Updated every batch. Sections: services, surface, theory (3 hypotheses + chosen), tested, next. Bullets, max 50 lines, prune old items to one-liners.

## Bookkeeping

experiments.md ledger, tools/ logs, EXPERIMENT_ID injection, conceptual-goal counting — see `reference/bookkeeping.md`.

## Creative Research (P2b)

Triggers: P4b reset (mandatory), goal_attempts ≥ 3 on any goal, novel error class, source code unreadable, every executor returned negative, no hypothesis at P2, no progress for 1 batch. See `reference/creative-research.md`. Most batches skip P2b.

## Spawning

See `reference/spawning-recipes.md` for copy-paste-ready spawn patterns per role. Context contracts in `reference/context-injection.md`. Role boundaries in `reference/role-matrix.md`.

## Roles

| Role | File | Context | When |
|------|------|---------|------|
| Executor (explore) | `reference/executor-role.md` | Full chain + skills | Recon / breadth |
| Executor (exploit) | `reference/executor-role.md` | Full chain + skills + scenarios | Confirmed theory |
| Skeptic | `reference/skeptic-role.md` | experiments.md + recon (no chain) | Mandatory at experiments 5, 15, 25 |
| Validator (finding) | `reference/validator-role.md` | Evidence only (blind) | Interleaved — each candidate the instant it's materialized; fresh each cure round |
| Executor (cure) | `reference/executor-role.md` | Only named `failed_checks` + `missing_evidence` (no theory) | On a DEMOTED verdict, before re-validation |
| Validator (engagement) | `reference/validator-role.md` | OUTPUT_DIR only (blind) | Once at loop end |

## Rules

1. **Autonomous.** Coordinator MUST NOT call `AskUserQuestion`. If a credential is missing, run `python3 tools/env-reader.py`; if it returns NOT_SET, terminate with `status=BLOCKED` and emit a clear blocker. Asking is the parent orchestrator's job.
2. **Think before acting.** Write 3 hypotheses (≥1 wildcard) to attack-chain.md before every batch. Record rejected ones — they are the search tree.
3. **Max 1-2 executors per batch.** Recon can use more.
4. **Pass chain context + specific PATT_URL** to executors. Not the full PATT map.
5. **30-experiment cap.**
6. **goal_attempts ≥ 3 on a conceptual goal** → P4b reset. Count by *goal*, not literal technique string. Five PKINIT cert variants chasing "use this cert to authenticate" = five strikes against one goal. See `reference/bookkeeping.md` for the goal column.
7. **Mandatory skeptic** at experiments 5, 15, 25 (see `reference/skeptic-role.md`).
8. **All output to OUTPUT_DIR.**
9. **Sequential flag progression** in multi-flag engagements. User-foothold first; root path usually flows from there.
10. **No partial completion as a success state.** A multi-flag engagement is incomplete until every flag submits. `status=FAILED_partial` is a temporary marker, never a final outcome.
11. **Phase 3 (skill-update + Slack + queue) is parent-orchestrator only.** Coordinator emits PHASE3_SUMMARY and exits.
12. **Source for library internals.** Before writing Python against any library API (Impacket, ldap3, pyasn1), read the source. Prefer CLI tools (secretsdump.py, ticketer.py, getST.py).
13. **Background command discipline.** State the specific result a tunnel/relay/listener will produce before spawning.
14. **Report gate.** Validated findings exist → Transilience PDF report required. Read `formats/transilience-report-style/pentest-report.md`.
15. **Validation completeness.** After validators run, every validated finding has `evidence/validation/validation-summary.md`. Flag any without proof.

## Token Discipline

- Internal output (chain, logs, reports): bullets, not prose.
- Executor prompts: 1-2 relevant skill files + the specific PATT_URL.
- attack-chain.md max 50 lines; bookkeeping max 10% of mission tokens.
- User-facing output (reports, summaries): detailed.

## References

`reference/principles.md` · `reference/preflight-checklist.md` · `reference/role-matrix.md` · `reference/bookkeeping.md` · `reference/spawning-recipes.md` · `reference/context-injection.md` · `reference/creative-research.md` · `reference/executor-role.md` · `reference/skeptic-role.md` · `reference/validator-role.md` · `reference/VALIDATION.md` · `reference/ATTACK_INDEX.md` · `reference/OUTPUT_STRUCTURE.md` · `reference/GIT_CONVENTIONS.md` · `formats/INDEX.md`

© transilienceai · MIT · transilienceai/communitytools

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set42

The whole set →
client-side The client-side skill tests web apps and SPAs for XSS, CSRF, CORS errors, clickjacking, DOM attacks, and Prototype Pollution. CX Codex +1 209installs reverse-engineering reverse-engineering guides disassembly and decompilation of ELF, PE, and Mach-O files to recover logic, emulate custom bytecode, and defeat binary obfuscation. CX Codex +1 203installs dfir dfir — a skill for analyzing Windows event logs, network captures, and filesystem artifacts during security incident investigations. Reconstructs Active Directory attack chains and builds timelines across multiple evidence sources. CX Codex +1 202installs essential-tools essential-tools — a skill for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode that loads pentesting methodology, Burp Suite, Playwright, Nuclei, and reporting standards into the agent context. CX Codex +1 202installs cloud-containers The cloud-containers skill checks AWS, Azure, GCP, Docker, and Kubernetes for security flaws. Use it to test a cloud target or review configuration with read-only credentials. CX Codex +1 197installs github-workflow The github-workflow skill brings GitHub operations to your AI assistant: branches, commits, pushes, pull requests, issues, and code review. Handy when you ask your agent to commit changes, push code, create a PR, or manage branches. CX Codex +1 195installs mobile-security mobile-security is a Claude Code skill that assesses Android and iOS apps against OWASP MASVS/MASTG through artifact review, runtime tests, and privacy checks. CX Codex +1 194installs system Skill for system-level security testing: Active Directory attacks, privilege escalation on Linux and Windows, exploit development. Built for penetration testers and security researchers. CX Codex +1 194installs

Project sponsors

Companies that keep this analytics open