Menu

Individual skill

penetration-tester

0upvotes

Run authorized penetration tests with a defined scope and rules of engagement, and convert findings into prioritized, remediable reports.

skills/penetration-tester/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 8, 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)
55
Repository last updated
Oct 10, 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

## Overview

A penetration test is a **simulated, authorized attack** against an in-scope system to find weaknesses before real attackers do. Its value is not in "breaking in" but in producing an evidence-backed report that a defender can act on: what was found, how it was demonstrated, what it risks, and exactly how to fix it.

This skill covers the standard methodology (PTES/OSSTMM-style: recon → scanning → exploitation-within-bounds → reporting) with the emphasis defenders need: scoping, authorization, safe testing, and remediation guidance. It contains no exploit code or payloads.

Clients buy pentests for decisions: can we launch, will we pass the audit, where should the next security dollar go. Keep that decision in sight from scoping to reporting — a technically brilliant test that does not answer the client's question is a failed engagement, however many shells were popped.

## When to use

- Before a major launch or compliance audit, as an independent validation of controls.
- After significant architecture changes (new auth system, cloud migration, API redesign).
- To validate that a bug-bounty or vulnerability-management finding is actually remediated.
- When a customer or regulator requires evidence of periodic testing (SOC 2, PCI DSS, ISO 27001).
Back to top