Individual skill

performing-penetration-testing

Route approved security work to the pack's 25 narrow operators, with authorization/scope gates, retained evidence and compatible report inputs. Use when starting a pentest, auditing dependencies or source code, checking an approved URL, or preparing engagement deliverables. Familiar requests route to the appropriate operator; retained legacy CLIs keep separate completion and JSON contracts. Trigger with "pentest", "security scan", "audit dependencies", "check headers", "find secrets", or "OWASP coverage".

plugins/security/penetration-tester/skills/performing-penetration-testing/SKILL.md

Read pinned source

Source commit 0500b275e963c027f6b410e8c49c0446945c574e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
2,917
Repository last updated
Nov 12, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Performing Penetration Testing

## Overview

Route an approved engagement across 25 narrow operator skills plus this
orchestrator. Each invoked CLI has its own arguments, evidence requirements
and exit status.

## Prerequisites

Use Read for approved ROE and saved findings, Glob/Grep to select artifacts,
and Write only for requested engagement outputs. These routing instructions
depend on each CLI's own input and evidence checks; reports do not certify
compliance.
Back to top