Skip to main content

Use with AI

Let an AI agent run the scan and read the results for you. The repo ships a Claude Code skill that drives ./pentest.sh and summarizes what it finds.

Authorized use onlyScan hosts you own or have written permission to test. Scanning systems without permission is illegal in most jurisdictions.

Start it​

Clone the repo (see Install & usage), open Claude Code in it, then ask:

pentest 192.168.1.10

You can also run /pentest. The skill lives in .claude/skills/pentest/SKILL.md and loads when you work in this repo.

note

The skill is a Claude Code feature. AGENTS.md and the Cursor rule in this repo don't contain the pentest procedure. Another agent can still follow the steps in SKILL.md by hand.

What the agent does​

  1. Confirms the target. If you didn't give a host, it asks.
  2. Confirms authorization. It only runs against hosts you own or have permission to test.
  3. Dry-runs first. It runs ./pentest.sh --target <host> --mode <mode> --dry-run and shows you the phases. It skips this only if you tell it to.
  4. Runs the scan. It runs the same command without --dry-run. The first run builds the pentest-tools image.
  5. Reports back. It tells you where the run folder is and summarizes report.md.

It defaults to quick for a first sweep and suggests full or web when a deeper look makes sense. If Docker isn't running, it tells you and suggests open -a Docker on macOS.

What it won't do​

  • Scan a target you haven't confirmed.
  • Scan a host without you confirming you own it or have permission.
  • Skip the dry-run unless you ask.

Why use it​

The findings table is made of pattern matches. It flags what's worth a look, and it misses anything the patterns don't cover. The agent reads the raw output files too, so it can pull out open ports and services, nikto hits, exposed directories, TLS weaknesses and SMB issues, then connect them to the table's recommendations.

Example​

Prompt:

pentest 192.168.1.10, quick mode, it's my home lab server

Example summary. The host and findings are made up:

Scan complete: log/192.168.1.10-2026-11-17_10-42-08/report.md

Open ports (nmap.txt)
- 22/tcp OpenSSH 9.2p1
- 80/tcp nginx 1.22.1
- 3493/tcp NUT upsd

Findings
- High: NUT upsd on 3493 is reachable from the network.
Set LISTEN 127.0.0.1 in /etc/nut/upsd.conf.
- Medium: plain HTTP on 80 with no redirect to HTTPS.

Next steps
- Fix the upsd listener, then re-run quick to confirm.
- Run web mode to check headers and exposed directories.