# Pentest Engagement

> Run a professional web/API/cloud penetration engagement from a scope file — mandatory surface expansion, systematic OWASP attack-class coverage, reversible active exploitation, root-cause severity, authoritative validation, and a Transilience PDF. The general (non-CTF) analogue of hackthebox/htb-solve.

- **Type:** Skill
- **Install:** `agentstack add skill-transilienceai-communitytools-pentest-engagement`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [transilienceai](https://agentstack.voostack.com/s/transilienceai)
- **Installs:** 0
- **Category:** [Content & Media](https://agentstack.voostack.com/c/content-and-media)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [transilienceai](https://github.com/transilienceai)
- **Source:** https://github.com/transilienceai/communitytools/tree/main/skills/pentest-engagement
- **Website:** https://www.transilience.ai/

## Install

```sh
agentstack add skill-transilienceai-communitytools-pentest-engagement
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Pentest Engagement

Orchestrates a scoped pentest end-to-end via the `pentest-engagement` workflow. It is the breadth-complete, coverage-gated counterpart to the flag-shaped `htb-solve` — same engines (`coordinator-loop`, `validate-findings`), but driven by an attack-class **coverage matrix** instead of a flag, with surface expansion and root-cause severity baked in.

## When to use
A web / API / cloud engagement defined by a **scope file** (assets, credentials, rules of engagement) — not a CTF/flag target. For HackTheBox/CTF use `hackthebox` (htb-solve) instead.

## Run it
```
Workflow('pentest-engagement', { scope_file: 'projects/pentest/-scope.md' })
```
or inline scope:
```
Workflow('pentest-engagement', { scope: { engagement_name, apex_domains:[], assets:[...], creds_env:[...], roe, business_tier } })
```
Options: `maxConcurrent` (default 3), `dryRun` (expand surface + work list only, no exploitation), `max_experiments`, `business_tier`, `report` (default true).

Write the scope file per [`reference/scope-file-format.md`](reference/scope-file-format.md). Credentials are referenced by **env-var name only** and read from the repo `.env` via `python3 tools/env-reader.py` — never inline secret values.

## Phases (what the workflow does)
1. **Setup** — `env-reader` creds, parse scope, `OUTPUT_DIR = projects/pentest/_/`, STARTED Slack (gated).
2. **Expand** *(the #1 fix)* — MANDATORY CT-log / passive-DNS / origin-discovery across every in-scope apex (`crt.sh`, `certspotter`, `subfinder`, origin-discovery for CDN/WAF-fronted hosts). Scope = the **discovered** surface, not the handoff. Builds the per-asset work list + seeds each asset's coverage matrix.
3. **Assess** — each asset → `coordinator-loop` in **coverage mode** (drives the OWASP API+Web attack-class matrix to completion; reversible active exploitation; root-cause severity) → `validate-findings` (authoritative).
4. **Correlate** — `attack-path-stitcher` + `risk-prioritiser` across all validated findings → ranked org roadmap.
5. **Report** — Transilience PDF over the validated + ranked set. COMPLETE only when **every** asset's coverage is satisfied; otherwise `INCOMPLETE_coverage` with the untested classes named.

## Boundaries
- Orchestrator only — never run the coordinator loop inline; the coverage/bookkeeping discipline needs the workflow boundary.
- A **missing credential is not a global block** — the unauthenticated surface is always tested; only a no-reachable-asset scope blocks.
- Reversible own-org/own-tenant writes are authorized by default (create-then-delete is non-destructive); destructive ops, DoS, brute force, and out-of-scope tenants are prohibited (set in RoE).

## References
- [scope-file-format.md](reference/scope-file-format.md) — scope file schema + worked example
- [coverage-matrix.md](../coordination/reference/coverage-matrix.md) — the canonical attack-class coverage contract (completion gate)
- [principles.md](../coordination/reference/principles.md) — scope-is-the-surface, reversible active exploitation, real-tools-first, root-cause severity
- [pentest-report.md](../../formats/transilience-report-style/pentest-report.md) — Transilience report structure + §7.1 root-cause severity
- [validator-role.md](../coordination/reference/validator-role.md) — engagement-validator attack-class coverage check (8)

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [transilienceai](https://github.com/transilienceai)
- **Source:** [transilienceai/communitytools](https://github.com/transilienceai/communitytools)
- **License:** MIT
- **Homepage:** https://www.transilience.ai/

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** yes
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-transilienceai-communitytools-pentest-engagement
- Seller: https://agentstack.voostack.com/s/transilienceai
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.