linux-pentester-command-reference — Claude Code skill
A skill that hands your agent a Linux command reference split by pentest phase: recon, enumeration, exploitation, privesc.
npx skills add reason-machines/security-skills --skill linux-pentester-command-reference -a claude-codeWhat linux-pentester-command-reference does
The skill points the agent at a collection of Linux commands and techniques grouped by phase. It covers daily survival commands, local and network recon, service and user enumeration, getting an initial shell, escalating to root, and post-exploitation work. A cheatsheet section holds quick one-liners.
The material sits in modules: 00-General-Commands, 01-Recon, 02-Enumeration, 03-Exploitation, 04-Privilege-Escalation, 05-Post-Exploitation and Cheatsheets. Ask about a specific phase and the agent pulls the matching folder instead of guessing from memory. Triggers include hunting SUID binaries, enumerating services on a target, and network discovery.
Worth installing if you poke at Linux boxes in labs or CTFs. These commands act on a live system, and some of them write files or leave traces, so run them against your own target only. The repository clones locally, which means the reference stays usable outside the agent too.
What it helps with
- hunt SUID binaries and judge which ones help with escalation
- enumerate services and versions on a Linux target
- gather local recon: processes, users, environment variables
- catch a reverse shell and stabilize the terminal
- check cron jobs and file permissions before escalating
Example prompts for the agent
- Show me Linux enumeration commands for pentesting
- How do I find SUID binaries for privilege escalation?
- What commands do I use for network reconnaissance on Linux?
How to install linux-pentester-command-reference
1Skills CLI (Vercel)
npx skills add reason-machines/security-skills --skill linux-pentester-command-reference -a claude-code2Manually: put the files in place
~/.claude/skills/linux-pentester-command-reference/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/linux-pentester-command-reference/
1Skills CLI (Vercel)
npx skills add reason-machines/security-skills --skill linux-pentester-command-reference -a codex2Manually: put the files in place
.agents/skills/linux-pentester-command-reference/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add reason-machines/security-skills --skill linux-pentester-command-reference -a cursor2Manually: put the files in place
.cursor/skills/linux-pentester-command-reference/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install reason-machines/security-skills linux-pentester-command-reference2Manually: put the files in place
.github/skills/linux-pentester-command-reference/SKILL.md1Skills CLI (Vercel)
npx skills add reason-machines/security-skills --skill linux-pentester-command-reference -a gemini-cli2Platform CLI
gemini skills install https://github.com/reason-machines/security-skills --path skills/linux-pentester-command-referenceManually: put the files in place
.devin/skills/linux-pentester-command-reference/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add reason-machines/security-skills --skill linux-pentester-command-reference -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about linux-pentester-command-reference
How do I install linux-pentester-command-reference in Claude Code?
Run npx skills add reason-machines/security-skills --skill linux-pentester-command-reference -a claude-code. The skill lands at ~/.claude/skills/linux-pentester-command-reference/SKILL.md.
What does linux-pentester-command-reference do?
It gives the agent a Linux command reference organized by pentest phase: reconnaissance, enumeration, exploitation, privilege escalation and post-exploitation.
Does it need network access while I work?
The reference is cloned locally, so you can read the commands without the agent. Some techniques assume a network path between your machine and the target.