Pentest

Skill FilippoDeSilva/skills/skills/pentest

Skills for my agentic development workflow.

Install

npx -y skills add FilippoDeSilva/skills --skill pentest

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

PTES-aligned adversarial security audit for backend, frontend, and mobile applications. Produces a CVSS-scored Hacker Report with verified PoCs and phased remediation.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.0 KB, 644 tokens by cl100k_base, as published. Nobody here has run it

Pentest Skill

[!IMPORTANT] PTES-aligned adversarial security audit for backend, frontend, and mobile applications. Produces a CVSS-scored Hacker Report with verified PoCs and phased remediation.

Optional args: slug=<feature>, ticket=<id/url>, mode=interactive|autonomous|channel, channel=<id>, auto_continue=true|false.

Instructions

When the user asks to perform this workflow, execute the following steps:

🕵️‍♂️ Penetration Test (PTES-Aligned)

Goal: Execute a red-team assessment across backend, frontend, and mobile targets with verified PoCs and audit-grade evidence.

Steps

Scope and authorization:
- Determine mode (whitebox, greybox, blackbox) and targets.
- Verify explicit authorization; stop if unauthorized.
Intel and threat model:
- Identify stack, endpoints, parameters, local storage, schemes, and secrets.
- Use common-security-audit, common-dast-tooling, and architecture docs when available.
- Map trust boundaries, secrets, external integrations, and privileged workflows before exploit attempts.
Vulnerability analysis:
- Run scans and delegate: SAST/SCA to specialist-aspm-correlator, dynamic/logic to specialist-logic-hacker, binary/mobile to specialist-mobile-reverser.
- Rank targets by exposure × sensitivity × auth_coverage.
Exploit verification:
- No Exploit = No Report. Discard unverified findings.
- Build reproducible PoCs and record preconditions, payloads, evidence, and blast radius.
Reporting:
- Write artifacts/security-review.md with assumptions, source provenance, review context, runtime contract, PoCs, blast radius, finding confidence, exploit path, evidence gaps, and handoff notes.
- Emit artifacts/security-review.dev.md, artifacts/security-review.appsec.md, or artifacts/security-review.exec.md only when leadership, client, or AppSec reporting is in scope.
- Score from 100: Critical -25 (cap 25), High -15 (cap 40), Medium -8, Low -3.
- Reuse the existing security-review.md record when pentest follows earlier design or PR security review work.
- Deliver findings in the standard template below.

Output Template

Executive Summary

Hacker Score: X/100 ([Critical/Vulnerable/Moderate/Hardened])
Target Scope: [repos, URLs, mobile apps]
Findings: [Critical/High/Medium/Low counts]

Findings Table

ID	Title	Platform	Severity	CVSS	CWE	PoC
SEC-01	[title]	[backend\|frontend\|mobile]	[Critical\|High\|Medium\|Low]	[score]	[CWE-id]	[Yes\|No]

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.