pentest-task-design

Orchestrates penetration testing workflows from reconnaissance through vulnerability verification to report generation.

632|86|Updated Apr 29, 2023
One-click install
npx skills add https://github.com/yaklang/yaklang --skill pentest-task-design-yaklang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pentest-task-design
Source: https://github.com/yaklang/yaklang/tree/main/common/ai/aid/aireact/skills/pentest-task-design
Command: npx skills add https://github.com/yaklang/yaklang --skill pentest-task-design-yaklang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Penetration testing involves many disconnected steps—reconnaissance, crawling, vulnerability probing, evidence collection, and reporting—and it is easy to skip phases or produce plans that never get executed. This Skill maps security testing methodology to concrete callable tools, defining a complete decision flow from target intake to final report. ## Core Features & Use Cases - Phased Task Orchestration: Guides the full lifecycle across reconnaissance (DNS, subdomain, WHOIS, port scan, crawler, TLS, fingerprinting), scope analysis, task planning, test execution, and report generation. - Tool-to-Task Mapping: Maps each testing step to specific tools such as scan_port, simple_crawler, do_http_request, brute, poc_template_searcher, and tls_inspect, with per-vulnerability execution flows for SQL injection, XSS, command injection, SSTI, IDOR, SSRF, and weak credentials. - Evidence-First Reporting: Enforces immediate vulnerability reporting via the cybersecurity-risk tool and organizes all artifacts into a structured recon/analysis/plan/results/report directory layout. - Use Case: Given a target like example.com, the Skill drives DNS enumeration, subdomain scanning, port scanning, web crawling, fingerprinting, prioritized test task generation, actual payload verification, and a severity-ranked pentest report. ## Quick Start Perform a security assessment of example.com, starting with reconnaissance and ending with a vulnerability report.

Frequently Asked Questions about pentest-task-design

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

FAQPage Schema
How do I run a penetration test against a website?▼

Start with reconnaissance: collect DNS records, enumerate subdomains, scan ports, crawl the web application, and fingerprint the tech stack. Then generate a prioritized task list covering SQL injection, XSS, command injection, and other tests, execute each with real HTTP requests, and compile a severity-ranked report.

How to test an API for SQL injection vulnerabilities?▼

Send a baseline request, then probe parameters with a single quote, boolean conditions (AND 1=1 vs AND 1=2), and time-delay payloads like SLEEP(5). If responses differ, confirm the database type and extract key evidence before recording the finding.

What tools are used for reconnaissance in penetration testing?▼

The reconnaissance phase uses dig for DNS records, subdomain_scan for subdomain enumeration, whois for registration data, scan_port for port and service discovery, simple_crawler for URL and form discovery, tls_inspect for certificate checks, and fingerprint matching for framework identification.

When should vulnerabilities be reported during a pentest?▼

Each confirmed vulnerability instance should be reported immediately via the cybersecurity-risk tool or written to an output evidence file, not batched at the end. For bulk enumeration like IDOR, report the first confirmed instance before continuing traversal.

What is the difference between planning mode and execution mode in security testing?▼

Planning mode produces task lists, priorities, and report frameworks when the user explicitly asks for a plan. Execution mode performs actual packet sending and vulnerability verification when the user requests testing, PoC validation, or exploit reproduction.