hackingtool

<div align="center">

<img src="images/logo.svg" alt="HackingTool" width="600">

hackingtool — Claude Code plugin

183 pentesting & OSINT tools at Claude's fingertips. Plugin-skill wrapper around Z4nzu/hackingtool. Runs locally on any OS — native Bash on Linux/macOS, WSL on Windows, or purpose-built Docker images (instrumentisto/nmap, projectdiscovery/nuclei, caffix/amass, and 20+ more). The skill picks the right backend and image automatically.

!Plugin !Tools !Categories !OS

Built by ariacodez · wraps Z4nzu/hackingtool (MIT)

</div>

See it in Action

<img width="1194" height="49" alt="image" src="https://github.com/user-attachments/assets/9a573541-eabb-4996-b305-c2c1f240cceb" /> <img width="1152" height="396" alt="image" src="https://github.com/user-attachments/assets/77b75859-7733-4807-9005-6bfcdd3340f5" /> <img width="1196" height="750" alt="image" src="https://github.com/user-attachments/assets/86c3b5a0-a016-4159-8580-9b96e5418e20" />

Install

/plugin marketplace add AKCODEZ/hackingtool-plugin
/plugin install hackingtool@hackingtool-marketplace

Then point Claude at a target:

"recon example.com"
"hunt the username johndoe"
"scan my repo for vulnerabilies"
"crack my own wifi before my neighbor does"

Claude picks the tools. You read the output.

How it works

Every tool invocation goes through ht_run.py, which:

1. Picks a backend: native (Linux/macOS), WSL (Windows + real distro), or Docker (anywhere Docker Desktop runs).
2. Maps known tools to purpose-built Docker images — fast pulls, clean ENTRYPOINTs, no apt install dance:

1. Runs the command, auto-retries with elevated privileges on permission errors (native/WSL), and surfaces the actual tool output as structured JSON.

The 🟢/🟡 icons in the inventory below are quick indicators of how the tool usually behaves — 🟢 for "plug-and-play" invocations, 🟡 for tools whose behavior depends on the backend and environment (adapter hardware, sudo config, etc.). Either way, the skill runs it and tells you what happened.

Current breakdown: 56 🟢 · 127 🟡 · 183 total.

OS support

The plugin picks a backend automatically via ht_env.py:

Docker images in the override map are pulled on first use and cached. ht_run.py <tool_id> --install runs the install commands for native/WSL when you need the binary on the host itself.

Master tool inventory

Legend: 🟢 plug-and-play · 🟡 depends on backend / environment

183 tools total — 🟢 56 plug-and-play · 🟡 127 environment-dependent

🛡 Anonymously Hiding (2)

🔍 Information Gathering (26)

📚 Wordlist Generator (7)

📶 Wireless Attack (13)

🧩 SQL Injection (7)

🎣 Phishing Attack (17)

🌐 Web Attack (20)

🔧 Post Exploitation (10)

🕵 Forensics (8)

📦 Payload Creation (8)

🧰 Exploit Framework (3)

🔁 Reverse Engineering (5)

⚡ DDOS (6)

🖥 RAT (1)

💥 XSS (9)

🖼 Steganography (4)

🏢 Active Directory (6)

☁ Cloud Security (4)

📱 Mobile Security (3)

✨ Other (1)

📱 Android Attack (5)

📧 Email Verifier (1)

🔑 Hash Crack (1)

🎭 Homograph (1)

🧪 Mix Tools (2)

💉 Payload Injection (2)

📱 Social Media (4)

🔎 Social Media Finder (4)

🕸 Web Crawling (1)

📡 Wifi Jamming (2)

Refreshing the tool index

When upstream hackingtool adds tools, regenerate data/tools.json and the README table:

python ${CLAUDE_PLUGIN_ROOT}/scripts/ht_index.py --hackingtool-path /path/to/hackingtool
python ${CLAUDE_PLUGIN_ROOT}/scripts/build_readme_table.py > new_table.md

If hackingtool is a sibling directory of this repo, --hackingtool-path isn't needed — the script auto-detects.

Directory layout

hackingtool-plugin/
├── .claude-plugin/
│   └── marketplace.json          # marketplace entry
├── images/                       # screenshots + logo
├── README.md                     # this file
└── plugins/hackingtool/
    ├── .claude-plugin/plugin.json
    ├── data/tools.json           # generated index
    ├── scripts/
    │   ├── ht_index.py           # (dev) regenerate tools.json
    │   ├── build_readme_table.py # (dev) regenerate the table above
    │   ├── ht_search.py          # query index
    │   ├── ht_env.py             # detect backend
    │   └── ht_run.py             # backend-aware tool runner
    └── skills/pentest/
        ├── SKILL.md
        └── reference/
            ├── workflows.md
            └── runtime-fallbacks.md

Limitations

• •Python 3.10+ required.
• •No async tool streaming. Long-running tools block until they finish or timeout.
• •Docker backend pulls kalilinux/kali-rolling on first use.
• •Capability flags are heuristics. If you find a mis-tagged tool, fix it in data/tools.json or open an issue.

Credits

• •Upstream toolkit: Z4nzu/hackingtool — all tool metadata, categorization, and screenshots originate from this project.
• •Plugin wrapper: ariacodez (AKCodez on GitHub).

License

MIT. Upstream Z4nzu/hackingtool is also MIT-licensed.

For authorized security testing, bug bounty, CTFs, and research only.