web-pentest

Conducts authorized web application penetration tests with phased recon, exploitation, and reporting.

1|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/brittb-dev/zerogravityclaw --skill web-pentest-brittb-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: web-pentest
Source: https://github.com/brittb-dev/zerogravityclaw/tree/main/src/hermes-core/optional-skills/security/web-pentest
Command: npx skills add https://github.com/brittb-dev/zerogravityclaw --skill web-pentest-brittb-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Security teams and developers need a disciplined, evidence-based way to test web applications they own for vulnerabilities, without producing unverified findings or accidentally attacking out-of-scope systems. ## Core Features & Use Cases - Phased Testing Workflow: Runs engagement setup, source pre-recon, live recon, vulnerability analysis, proof-based exploitation, and professional reporting in sequence. - Hard Guardrails: Enforces written authorization, scope allowlists, rate limiting, destructive-payload approval, and credential redaction before any active request is sent. - Proof-Based Findings: Requires reproducible witness payloads and bypass-set exhaustion before confirming or dismissing any vulnerability, with CVSS scoring only for verified L3/L4 findings. - Use Case: Point the agent at your staging application, confirm authorization, and receive a structured pentest report with verified SQLi, XSS, IDOR, or SSRF findings including reproduction curl commands and remediation guidance. ## Quick Start Ask the agent to pentest your staging web application at a given URL and confirm you own it when prompted for authorization.

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?▼

Declare the target URL, confirm in writing that you own or are authorized to test it, and the workflow builds a scope allowlist before any active scanning. It then runs recon, vulnerability analysis, and proof-based exploitation phases, ending with a structured report.

What vulnerability classes does web application pentesting cover?▼

The analysis covers injection (SQLi, command, SSTI, path traversal), XSS (reflected, stored, DOM), authentication flaws, authorization issues like IDOR, SSRF, and infrastructure misconfigurations. Each class maps to the OWASP Top 10 for reporting.

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

No, production systems require explicit written sign-off and third-party services are out of scope by default. The workflow refuses any request to hosts not listed in the engagement scope file and stops on off-scope redirects.

Why does a pentest report exclude unverified findings?▼

The methodology requires reproducible proof before confirming a vulnerability, so pattern-matched candidates without behavioral evidence stay as L1/L2 candidates. CVSS scores are only assigned to verified L3/L4 findings to avoid false-positive noise.

What are the limitations of automated web pentesting?▼

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