by 0x45dd
Autonomous agentic network penetration-testing tool (authorized use only)
From $49 · 30 days · terms & refunds
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
Automated security scan — not a certification.
# Add to your Claude Code skills
git clone https://github.com/0x45dd/pwnerGuides for using ai agents skills like pwner.
Last scanned: 11/5/2026
{
"issues": [
{
"file": "README.md",
"line": 137,
"type": "remote-install",
"message": "Install command (remote install script piped to a shell — review the source before running): \"curl -fsSL https://raw.githubusercontent.com/0x45dd/pwner/main/install.sh | bash\"",
"severity": "low"
}
],
"status": "PASSED",
"scannedAt": "2026-11-05T11:53:35.281Z",
"npmAuditRan": true,
"pipAuditRan": false,
"promptInjectionRan": true
}See how pwner compares with popular alternatives.
pwner is an LLM-driven agent that plans and runs a network penetration test from your
terminal. It discovers hosts, fingerprints services, checks them against known issues, and —
when the target warrants it and you approve — exploits them to prove impact. It drives
real tools (nmap, nuclei, netexec, impacket, hydra and others) rather than simulating them,
and it reports confirmed findings with severity, evidence and a fix.
It runs on your own model, or on no model at all.
--no-ai runs the full discovery → fingerprint → detect pipeline
deterministically, with no API key and nothing leaving the machine.Two mechanisms, both in the tool layer, both outside the model's reach. The model can ask for anything; it cannot widen its own authorization.
flowchart LR
OP(["operator"]) -->|"plain language"| AG["agent loop"]
AG -->|"tool call"| SG{"scope guard"}
SG -->|"host outside<br>the target"| R1["refused"]
SG -->|"in scope"| CG{"consent gate"}
CG -->|"intrusive,<br>not approved"| R2["skipped"]
CG -->|"approved, or<br>not intrusive"| RUN["runs against<br>the target"]
classDef guard fill:#ffb000,stroke:#8a5f00,color:#140d00,stroke-width:2px
classDef stop fill:none,stroke:#8b949e,stroke-dasharray:4 4
class SG,CG guard
class R1,R2 stop
A refusal is not an error that stops the run: it goes back to the model as a tool result, so the agent learns it overstepped and carries on inside the boundary.
Scope lock. build_dispatch wraps every tool so each
host-carrying argument is checked against your target before the tool body runs. Tools are
in-scope-by-default: one that forgets its own check is still guarded, and an unregistered
tool name fails closed. A network argument has to sit entirely inside the authorization, so
a /24 scope cannot be widened to a /16 by a tool argument.
Changing the scope. The one thing the guard cannot check is set_target, because its
argument is the new scope, so there is nothing to check it against. It carries its own
gate instead: narrowing, or returning to something you already authorized, is free, and
moving anywhere else needs your answer every time. An earlier approval for some other
action does not buy it, --auto-consent does not cover it, and a non-interactive run
refuses it outright.
Consent gate. Anything active is denied unless you approve it in that session. The agent
cannot self-approve — consent is resolved outside the model — and a non-interactive run
refuses it unless you launched it with --auto-consent.
These two are the part of the codebase under the most test: 77 tests on the scope boundary
in tests/test_scope.py, 32 more on the scope-change gate in
tests/test_scope_change.py, and 13 on the consent gate in
tests/test_consent.py, out of 785 overall. If you are going to
read one thing before pointing this at a network, read those.
Intended use:
Not this tool's purpose, and not defensible:
Python 3.10+. nmap is the only hard requirement — everything else enables more tools and is optional.
curl -fsSL https://raw.githubusercontent.com/0x45dd/pwner/main/install.sh | bash
That builds an isolated virtualenv under ~/.local/share/pwner, leaves your system
Python alone, and puts pwner on your PATH so it works from any directory. Add
--with-tools to install nmap and the optional scanners too, and --uninstall to take
it all back out.
It is on PyPI too, if you would rather use your own Python tooling:
pipx install pwner # isolated, and `pwner` lands on your PATH
uv tool install pwner # the same, through uv
pip install pwner # inside a virtualenv
Reach for pipx or uv tool over a bare pip install: they give you the same isolation
the installer script does, and installing into the system Python is refused outright on
most current distributions anyway.
On macOS there is also a tap:
brew install 0x45dd/tap/pwner
That brings nmap with it. From source instead:
git clone https://github.com/0x45dd/pwner.git
cd pwner
python3 -m venv .venv && source .venv/bin/activate
pip install -e .
Then the external tools, and a check:
./scripts/install-deps.sh # brew/apt/kali/pacman/dnf
pwner doctor # what's missing
install-deps.sh installs only what is missing and skips anything your distro does not
package instead of failing. pwner doctor reports every external tool, what each one
enables, and the install command for the system you are on; it exits non-zero only when
nmap is missing, so it works as a setup check in a script.
On Kali there is almost nothing to install. A default Kali image already ships 8 of the
11 external tools pwner drives — nmap, hydra, netexec, impacket, certipy, searchsploit,
hashcat and snmpwalk. sudo apt install nuclei bloodhound.py adds two more, and only
kerbrute is unpackaged. pwner detects Kali as its own ecosystem rather than as Debian, so
pwner doctor hands you apt commands instead of the source builds a plain Debian box needs.
If you are choosing where to run this, run it there.
uv tool install pwner # from PyPI, command on your PATH
uv venv && uv pip install -e . # from a clone, editable
pipx install -e . # from a clone, command on your PATH
The whole toolchain in one image, nothing installed on your host. The base is Kali, so every tool but kerbrute comes from apt:
docker build -t pwner .
docker run --rm -it --net=host \
--cap-add=NET_RAW --cap-add=NET_ADMIN \
-v pwner-config:/root/.config/pwner \
-v pwner-sessions:/root/.local/share/pwner \
pwner
--net=host and the two capabilities are what let nmap do SYN scans and ICMP/ARP discovery;
without them it quietly falls back to slower connect scans and finds fewer hosts. The
volumes persist your key and your saved transcripts.
The image is ~2.7 GB and carries 10 of the
pwner is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by 0x45dd. Autonomous agentic network penetration-testing tool (authorized use only). It has 84 GitHub stars.
Yes. pwner passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/0x45dd/pwner" and add it to your Claude Code skills directory (see the Installation section above).
pwner is primarily written in Python. It is open-source under 0x45dd on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh pwner against similar tools.
No comments yet. Be the first to share your thoughts!