web-pentest

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires nmap, whatweb, curl, 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 provides a phased penetration testing workflow that prevents off-scope testing, eliminates unverified findings, and produces professional reports with proof-of-concept evidence for each vulnerability. ## Core Features & Use Cases - Authorization-Gated Workflow: Requires written operator confirmation and maintains a machine-readable scope allowlist before any active scanning begins, with fail-closed host checking on every request. - Proof-Based Exploitation: Follows a "No Exploit, No Report" methodology where findings are promoted through levels (identified, partial, confirmed, critical) only with reproducible witness payloads, and false positives require bypass-set exhaustion. - Structured Reporting: Generates CVSS-scored findings with request/response evidence, reproduction steps, and remediation guidance using standardized templates. - Use Case: A developer wants to security-test their staging application before launch. The Skill sets up an engagement directory, records authorization, runs rate-limited recon with nmap and whatweb, analyzes six vulnerability classes (injection, XSS, auth, authz, SSRF, infra), confirms exploitable issues with minimal witness payloads, and produces a professional pentest report. ## Quick Start Ask the agent to pentest your staging application URL and reply "authorized" when prompted to confirm ownership and begin the engagement.

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

Provide the target URL and confirm in writing that you own or have authorization to test it. The workflow creates an engagement directory, records authorization, builds a scope allowlist, then runs recon, vulnerability analysis, proof-based exploitation, and reporting phases.

What vulnerability classes does web application pentesting cover?▼

The analysis covers six classes: injection (SQLi, command, SSTI, path traversal), XSS (reflected, stored, DOM), authentication flaws, authorization issues (IDOR, privilege escalation), SSRF, and infrastructure misconfigurations, mapped to the OWASP Top 10.

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

Production systems require explicit written sign-off and are excluded by default. Third-party APIs, cloud metadata endpoints, and multi-tenant systems are out of scope unless explicitly listed in the engagement authorization.

Why does the pentest refuse to scan certain hosts?▼

Every active request is checked against the scope.txt allowlist before sending. Hosts not explicitly listed, redirect targets leaving scope, and cloud metadata IPs are refused by default to prevent unauthorized testing.

What are the limitations of automated web pentesting?▼

It does not cover network-layer attacks, reverse engineering, source-only static analysis, or social engineering. Findings are time-bounded and method-bounded, so a clean report means no exploitable issues were found, not that the application is secure.