Z4nzu/hackingtool

Maintainer? Show your league in your README

Card: your league's emblem, from Copper to Legendary

[![bestofgithub](https://bestofgithub.dev/badge/Z4nzu/hackingtool.svg?style=card)](https://bestofgithub.dev/repo/Z4nzu/hackingtool)

Flat: fits beside your other badges

[![bestofgithub](https://bestofgithub.dev/badge/Z4nzu/hackingtool.svg)](https://bestofgithub.dev/repo/Z4nzu/hackingtool)

Loading README…

#	Category	Tools	#	Category	Tools
1	🛡 Anonymously Hiding Tools	5	12	🔁 Reverse engineering tools	10
2	🔍 Information gathering tools	26	13	⚡ DDOS Attack Tools	7
3	📚 Wordlist Generator	8	14	🖥 Remote Administrator Tools (RAT)	4
4	📡 Wireless attack tools	17	15	🧪 XSS Attack Tools	6
5	💉 SQL Injection Tools	7	16	🖼 Steganography Tools	10
6	🎣 Phishing attack tools	13	17	🏢 Active Directory Tools	10
7	🌐 Web Attack tools	23	18	☁ Cloud Security Tools	7
8	🔧 Post exploitation tools	15	19	📱 Mobile Security Tools	6
9	🕵 Forensic tools	12	20	✨ Other tools	10
10	📦 Payload creation tools	6	21	🔑 Password / Hash Cracking	7
11	🧰 Exploit framework	6

Dependency	Version	Needed for
Go	1.21+	nuclei, ffuf, amass, httpx, katana, dalfox, gobuster, subfinder
Ruby	any	haiti, evil-winrm
tmux	any	background panes (`/run … &`, `/panes`, `/attach`)
Docker	any	Mythic, MobSF (optional)

You type	It means	Example
`/…`	a command you run	`/search subdomain`
`@…`	a thing you name	`@nmap`, `@tag:osint`
anything else	plain English "what I want to do"	`crack a wifi handshake`

Command	Aliases	What it does
`/run <tool> [args] [&]`	`/open`	open a tool's menu; with a trailing `&` it runs in a background tmux pane instead (that's where `args` are used)
`/search <keyword>`		search tools by name, description or tag
`/tags`		list every tag with its tool count
`/ai <goal>`	`/recommend`, `/r`	recommend tools for a goal
`/goal <objective>`		AI-plan an objective and run it step by step, with per-step confirmation
`/find <need>`	`/discover`	find tools for a need — your catalog first, then GitHub (suggest-only)
`/panes`	`/jobs`	list background panes
`/attach`		attach to the background session (`Ctrl-b` `d` to return)
`/kill <label\|all>`		kill one background pane, or all of them
`/config [key value]`		view/change settings; `/config test` checks the AI connection, `/config github` checks the GitHub token
`/skill`		show the operator playbook
`/update` · `/uninstall`	`/remove`	update system packages or hackingtool · remove hackingtool and its tools
`/clear`	`/cls`	clear the screen
`/back`	`/b`	leave the current tool and go back
`/help`	`/?`, `/h`	quick reference card
`/quit`	`/q`, `/exit`	exit (also `q`, `Ctrl-C`, `Ctrl-D`)
`@<tool>`		open a tool (case-insensitive, fuzzy fallback)
`@tag:<tag>`		list and pick from the tools carrying that tag

Document	What's in it
How to use hackingtool	numbered walkthroughs: first run, `/find`, `/goal`, `/config`, background panes, headless mode
Tool catalog	every tool, by category, with links and tags
Operator playbook	the charter and grounding rules the AI layer runs under (also `/skill`)
SECURITY.md	disclosure policy, release verification, threat model
CONTRIBUTING.md	catalog-first tool additions, the gate your PR must pass

Z4nzu/hackingtool

AI-guided, all-in-one toolkit for authorized security testing

Contents

Why hackingtool

Tool Categories

Installation

From source with pipx (recommended)

For development

Docker

Optional runtimes

Quick Commands

Command reference

Features

🔎 `/find` — a tool for a need you don't have yet

🎯 `/goal` — plan an objective, run it one step at a time

🧠 Recommendations — say what you want in plain English

🏷 Tags and search

▶ Background panes (tmux)

⚙ Settings and the AI layer

📋 Headless engagements

Documentation

Contributing

Support & Sponsor

Social

I want to…	Do this
💡 Suggest a tool	Open a Tool Request issue
➕ Add a tool	Add a catalog entry (or a class for custom install/run logic), then open a PR with the template
🐛 Report a bug	Open a Bug report issue
🔒 Report a vulnerability	Privately — do not open a public issue; see SECURITY.md