Files
hackingtool/docs/TOOLS.md
T
Hardik Zinzuvadiya 2482cc9fd0 feat: AI operator console — 215 curated tools, AI layer, /find discovery (v2.0.0 rework)
Squashed rework of hackingtool from a tool launcher into an AI-guided operator
console for authorized security testing. 93 commits collapsed into this one;
the pre-rework tree is tagged v2.0.0.

CATALOG & ENGINE
- Data-driven YAML catalog (21 categories, 215 live tools + 59 archived) with a
  registry/overlay loader and a fixed 66-tag taxonomy (63 in use). Adding a tool
  is one YAML entry, not edits across the codebase.
- Engine honesty: real exit codes, truthful install success/failure, reuse-first
  skip, EOF-safe prompts, command audit logging.
- Safe installs: sha256-required safe-fetch (killed `curl | bash` in feroxbuster,
  Caido and Sliver), list-form subprocess only, no forced sudo.

AI LAYER (bring-your-own-key or local model; degrades offline, never fabricates)
- AI1 intent -> tools; AI2 tool+goal -> command, curated-first with a grounded
  fallback; AI3 findings summary and engagement report; AI4 per-finding impact
  and remediation. Prompt-injection hardened per OWASP LLM01.
- /goal plans an objective and runs it one step at a time, showing every command
  before it runs, with a plan.json + run.log audit trail.

/find TOOL DISCOVERY (this branch's headline feature)
- Suggests real GitHub projects when the catalog has no tool for a need.
  Deterministic: zero model calls, structured API fields only, suggest-only —
  it never clones, installs or runs anything.
- A charter filter refuses destructive/DoS/jamming/mass-targeting/evasion asks
  before any network I/O, while a defensive-intent guard keeps blue-team and
  DFIR phrasing ("detect a SYN flood in a pcap") from being false-refused.
- Query rewriting proved to be the dominant quality lever (the first design
  measured 29% precision with no results on 5 of 8 needs): a curated 41-row
  intent table maps plain English to canonical jargon plus a GitHub topic, and
  a two-arm search unions topic coverage with jargon precision.
- Explainable additive ranking: log-flattened stars, license/age/language,
  trusted-author bonus derived from owners we already ship, docs-repo demotion
  by name, staleness as a soft demotion rather than a filter (a hard cutoff
  would delete THC-Hydan and John the Ripper), and a relevance term weighting
  curated topics above free-text description.
- Optional no-scope GitHub token purely as a rate-limit lever (10 -> 30 req/min);
  it reaches only an Authorization header, never a cache key, log or output.
- `[a]` saves a pick to ~/.hackingtool/found.yaml as a structurally inert entry,
  and the loader strips executable keys from user catalogs at read time so a
  hand-edited file cannot become a runnable command.

CONSOLE & PACKAGING
- REPL with a / command palette, @ tool mentions, tag filters, history and
  completion; background tmux panes; settings and first-run scaffolding.
- src-layout package with catalog and pipelines as package data, console entry
  point, Docker image, signed releases with SBOM and build provenance.
- Health docs (SECURITY, CONTRIBUTING, CHANGELOG, CODE_OF_CONDUCT), a CI gate
  (ruff + pytest + catalog/taxonomy conformance) and a pre-push hook.
- README rewritten with a section index, the tool catalog split into
  docs/TOOLS.md and a step-by-step docs/HOW-TO-USE.md.

278 tests passing; scripts/check.sh green.
2026-07-27 00:18:34 +05:30

27 KiB

Tool catalog

Every tool hackingtool can install, launch, or point you at — 215 active tools across 21 categories, plus 59 archived entries kept out of this list (they are unmaintained or dead upstream and are hidden in the app unless you set show_archived true via /config).

Tags under each entry come from the fixed taxonomy in src/hackingtool/tags.py (63 tags in use). Inside the app you can filter by any of them with @tag:<name>, or search names/descriptions/tags with /search <keyword>.

Entries marked as a link point at the upstream project; a few are curated reference resources (labs, cheat sheets, online services) rather than installable binaries — hackingtool opens those instead of installing them.

Authorized targets only. Every tool here is for systems you own or have written permission to test.

Back to the README · How to use hackingtool


🛡 Anonymously Hiding Tools

🔍 Information gathering tools

📚 Wordlist Generator

📡 Wireless attack tools

💉 SQL Injection Tools

🎣 Phishing attack tools

🌐 Web Attack tools

🔧 Post exploitation tools

🕵 Forensic tools

📦 Payload creation tools

🧰 Exploit framework

🔁 Reverse engineering tools

DDOS Attack Tools

🖥 Remote Administrator Tools (RAT)

🧪 XSS Attack Tools

🖼 Steganography Tools

🏢 Active Directory Tools

☁ Cloud Security Tools

📱 Mobile Security Tools

Other tools

🔑 Password / Hash Cracking


Adding a tool

Most tools are one YAML entry in src/hackingtool/catalog/ — no Python. See CONTRIBUTING.md for the entry format, the tag taxonomy, and the checks your PR has to pass (make check).

Can't find what you need? Ask the console: /find <what you're trying to do> searches the catalog first, then GitHub, and shows real maintained repos with the reason each was ranked. See HOW-TO-USE.md.