web-pentest

Runs authorized web application penetration tests with scoped recon, proof-based exploitation, and reporting.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/loteiron/ZeusAgent --skill web-pentest-loteiron
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: web-pentest
Source: https://github.com/loteiron/ZeusAgent/tree/main/optional-skills/security/web-pentest
Command: npx skills add https://github.com/loteiron/ZeusAgent --skill web-pentest-loteiron

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires nmap, whatweb, and includes scripts (resource) and references (resource) components.

What problem does it solve? Web application security testing requires strict authorization controls, disciplined scope enforcement, and reproducible evidence for every finding. This Skill structures the entire engagement so no active request leaves the authorized scope and no vulnerability is reported without a working proof-of-concept. ## Core Features & Use Cases - Phased engagement workflow: Moves through engagement setup, optional source pre-recon, live read-only recon, per-class vulnerability analysis, proof-based exploitation, and report generation. - Scope and authorization enforcement: Requires written operator authorization, maintains a scope.txt allowlist, and refuses off-scope hosts via the recon-scan.sh wrapper script. - Evidence-based findings: Promotes candidates through L1-L4 verification levels, requires bypass-set exhaustion before dismissing false positives, and produces a CVSS-scored report from templates. - Use Case: Point the agent at your staging application, confirm authorization, and receive a structured pentest report covering SQLi, XSS, auth, IDOR, SSRF, and infrastructure misconfigurations with reproducible curl commands for each confirmed finding. ## Quick Start Ask the agent to pentest your staging application URL and reply "authorized" when prompted to confirm ownership and scope.

Frequently Asked Questions about web-pentest

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an authorized penetration test on my web app?▼

Start by confirming in writing that you own or have authorization to test the target, then record it in engagement/authorization.md and build a scope.txt allowlist. The workflow proceeds through recon, vulnerability analysis, proof-based exploitation, and reporting phases.

What vulnerability classes does web pentest automation cover?▼

The analysis phase covers six classes: injection (SQLi, command, SSTI, path traversal), XSS (reflected, stored, DOM), authentication (JWT attacks, session flaws), authorization (IDOR, privilege escalation), SSRF, and infrastructure misconfiguration.

Does the pentest skill work against production systems?▼

Production testing is refused by default unless the operator explicitly confirms written sign-off. Default targets are staging environments, local docker instances, and dedicated test systems listed in the scope allowlist.

Why does the skill require proof before reporting vulnerabilities?▼

Findings must reach L3 (confirmed behavior change) or L4 (data extracted or access escalated) with a reproducible request/response pair before receiving a CVSS score. Pattern-matched candidates without proof are listed separately as unverified.

What are the limitations of automated web pentesting?▼

It excludes network-layer attacks, reverse engineering, static-only source analysis, and social engineering. Even a clean run only means no exploitable issues were found within the given scope, time, and methods, not that the application is secure.