web-pentest

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

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/vivekgoquest/hermes-agent-stable --skill web-pentest-vivekgoquest
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: web-pentest
Source: https://github.com/vivekgoquest/hermes-agent-stable/tree/main/optional-skills/security/web-pentest
Command: npx skills add https://github.com/vivekgoquest/hermes-agent-stable --skill web-pentest-vivekgoquest

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Manual web application penetration testing is slow, inconsistent, and easy to do unsafely. This Skill enforces a disciplined, authorization-gated pentest workflow where every finding requires reproducible proof and every active request stays inside a pre-declared scope. ## Core Features & Use Cases - Phased engagement workflow: Moves through engagement setup, optional source-code pre-recon, live read-only recon, per-class vulnerability analysis, proof-based exploitation, and structured reporting. - Hard safety guardrails: Requires written authorization before scanning, enforces a scope.txt allowlist on every request, rate-limits traffic, and demands approval for destructive payloads. - Proof-based findings: Promotes candidates through L1-L4 evidence levels and only reports L3/L4 findings with CVSS scoring, request/response proof, and reproduction steps. - Use Case: Point the agent at your own staging application, confirm authorization, and receive a structured pentest report covering SQLi, XSS, auth, IDOR, SSRF, and infrastructure misconfigurations with curl reproducers for each confirmed finding. ## Quick Start Ask the agent to pentest your staging application URL and reply authorized when it presents the engagement confirmation prompt.

Frequently Asked Questions about web-pentest

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

FAQPage Schema
How do I run a penetration test on my own web application?▼

Start the engagement by giving the agent your target URL, then confirm in writing that you own or are authorized to test it. The skill builds a scope allowlist, runs read-only recon with nmap and whatweb, stages vulnerability candidates, and only fires minimal witness payloads after authorization is recorded.

What vulnerability classes does a web pentest cover?▼

This workflow covers injection (SQLi, command, SSTI, path traversal, deserialization), reflected/stored/DOM XSS, authentication and JWT attacks, authorization flaws like IDOR and privilege escalation, SSRF, and infrastructure misconfigurations mapped to the OWASP Top 10.

Can I pentest production systems or third-party services?▼

No. Production systems require explicit written sign-off, and third-party APIs, SaaS dependencies, and cloud metadata endpoints are out of scope by default. Every active request must match a hostname or CIDR in the engagement scope.txt file.

How are pentest findings verified before reporting?▼

Findings are promoted through evidence levels from identified to critical, and only L3/L4 findings with observable behavior change appear in the report. Blocked payloads must exhaust a documented bypass set before being classified as false positives.

What are the limitations of automated web pentesting?▼

The skill excludes network-layer attacks, reverse engineering, pure static analysis, and social engineering. A clean result means no exploitable issue was found within the scope, time, and methods used, not that the application is secure.