Agent skill · security · aradotso
linux-pentester-commands
Practical Linux command reference for penetration testing, reconnaissance, enumeration, exploitation, and privilege escalation
Why this skill is useful
Provides a curated collection of niche Linux commands specifically for penetration testing workflows that the AI wouldn't reliably generate on its own.
What it needs
Requires git installed locally. About 6k tokens when loaded. Last updated 2026-08-04. 11 stars on the source repository.
What this skill does
Linux Pentester Commands Skill Skill by ara.so — Security Skills collection. This skill provides expertise in using the Linux for a Pentester command reference repository, a curated collection of practical Linux commands used in penetration testing workflows including reconnaissance, enumeration, exploitation, privilege escalation, and post-exploitation. What This Project Does Linux for a Pentester is a practical command reference organized by penetration testing phases: General Commands: Essential Linux survival commands Reconnaissance: Local and network information gathering Enumeration: Deep service and user data discovery Exploitation: Initial access techniques Privilege Escalation: Techniques to gain root access Post-Exploitation: Persistence and lateral movement Cheatsheets: Quick reference one-liners Installation Clone the repository to have offline access during engagements: For quick reference during active testing: Repository Structure Common Pentesting Workflows 1. Initial Reconnaissance System Information Gathering: Network Reconnaissance: 2. Enumeration Phase User Enumeration: Service Enumeration: File System Enumeration: 3. Exploitation Commands Reverse Shells: Shell Upgrade: 4. Privilege Escalation SUID Exploitation: Sudo Exploitation: Cron Job Exploitation: Kernel Exploits: 5. Post-Exploitation Credential Harvesting: Persistence: Key Command Categories Network Scanning File Transfer Techniques Log Cleanup Environment Variables When working with this reference, consider setting these environment variables in your testing environment: Troubleshooting Common Issues Command Not Found Some commands may not be available on minimal systems: Permission Denied Errors Limited Shell Issues Best Practices 1. Always redirect errors when searching: 2>/dev/null 2. Use /tmp or /dev/shm for temporary files (usually writable) 3. Clean up after testing to avoid detection 4. Document findings as you discover them 5. Test commands in safe environments first 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aradotso/linux-pentester-commands