offensive-toolkit
Skill4 starsChanged 3 months agoMITView on GitHub
Use hackingtool — a 21-category, 173-tool offensive security and pentesting
- Installs packages
In this repository80 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/security-agent-skills.mdcCursor rule
- ai-mcp-securitySkill
- modern-attack-surfacesSkill
- security-and-hardeningSkill
- security-auditSkill
- security-code-reviewSkill
- ctf-jail-escapeSkill
- ctf-kernel-exploitationSkill
- ctf-misc-toolkitSkill
- ctf-orchestratorSkill
- ctf-playbookSkill
- ctf-technique-atlasSkill
- ctf-training-loopSkill
- ctf-web-exploitationSkill
- ctf-writeup-disciplineSkill
- ctf-writeup-screenshotsSkill
- binary-exploitationSkill
- crypto-attack-patternsSkill
- crypto-ctf-attacksSkill
- cryptography-fundamentalsSkill
- crypto-toolkitSkill
- encoding-realignmentSkill
- exploit-developmentSkill
- exploit-poc-builderSkill
- kernel-exploitationSkill
- zero-day-huntingSkill
- bluetooth-jammer-sweepSkill
- esp32-serial-diagSkill
- flipper-zero-backupSkill
- flipper-zero-firmwareSkill
- hardware-iot-hackingSkill
- nrf24-bitbang-spiSkill
- rf-jammer-firmware-portSkill
- rf-multi-protocol-jammerSkill
- smart-card-driver-debugSkill
- smart-card-usb-directSkill
- wifi-deauth-jammerSkill
- wifi-dualband-jammerSkill
- advanced-pentestSkill
- network-pentestSkill
- pentest-quick-checklistSkill
- pentest-tool-referenceSkill
- pentest-tool-setupSkill
- pentest-workflowSkill
- advanced-attack-chainsSkill
- autonomous-pentest-scannerSkill
- intranet-pentest-advancedSkill
- pentest-report-generatorSkill
- post-exploitation-opsSkill
- professional-pentest-guideSkill
- chatgpt-web-relaySkill
- darkweb-researchSkill
- email-osint-investigationSkill
- local-network-reconSkill
- network-device-reconSkill
- osint-frameworkSkill
- osint-recon-modelSkill
- parallel-intel-gatheringSkill
- reconnaissance-opsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 33
macOS caveats: No brew on system PATH → pkg_mgr is empty.
- Distinctive: line 126
If user asks "what tools for X?", search or use tags to find matches.
- Distinctive: line 127
If user asks "list all tools in category Y", programmatically enumerate that category.
- Distinctive: line 128
If user asks "install tool Z from hackingtool", explain that hackingtool's install wrappers target Linux (apt/brew), but Hermes can install …
- Very specific: line 129
If user asks "run hackingtool", remind them to use the hackingtool command from an interactive terminal (the TUI needs stdin).
- Distinctive: line 130
If user asks "search hackingtool for KEYWORD", use the programmatic search method above.
- Very specific: line 133
Never try hackingtool --help in a non-TTY — it will hang on Prompt.ask.
- Very specific: line 137
Do NOT use sudo with hackingtool — the venv install is user-local.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
HackingTool — Offensive Security Suite
Purpose
hackingtool is a comprehensive offensive security toolkit (173 tools across 21 categories). Installed locally at ~/hackingtool/ in a venv; launcher at ~/.local/bin/hackingtool.
Installation Details
- Source:
git clone https://github.com/Z4nzu/hackingtool.git ~/hackingtool - Venv:
~/hackingtool/venv(Python 3.11, dependencies fromrequirements.txt) - Launcher:
~/.local/bin/hackingtool(bash, auto-activates venv, on PATH) - User config:
~/.hackingtool/config.json(tools_dir, go_bin_dir, etc.) - macOS caveats: No brew on system PATH →
pkg_mgris empty; most tools need manual Homebrew installs. Wireless attacks (airgeddon, fluxion, etc.), AD/Linux-only tools, and hardware-dependent tools will fail to install but the TUI still works for discovery.
How to Interact
1. Interactive TUI (for the USER, not for Hermes)
hackingtoolThis opens the Rich-based TUI. The user navigates with numbers, /query for search, t for tag filtering, r for task recommendations, ? for help, q to quit.
2. Programmatic Tool Listing (Hermes internal)
List categories and all tools:
~/hackingtool/venv/bin/python3 -c "
import sys; sys.path.insert(0, '~/hackingtool')
from hackingtool import all_tools
for cat in all_tools:
print(cat.TITLE)
if hasattr(cat, 'TOOLS'):
for t in cat.TOOLS:
print(f\" {t.TITLE}\")
"3. Search Tools by Keyword
~/hackingtool/venv/bin/python3 -c "
import sys; sys.path.insert(0, '~/hackingtool')
from hackingtool import _collect_all_tools
query = 'KEYWORD'.lower()
for tool, cat in _collect_all_tools():
if query in tool.TITLE.lower() or query in (tool.DESCRIPTION or '').lower():
print(f'{tool.TITLE} [{cat}] — {tool.DESCRIPTION.splitlines()[0]}')
"4. Filter by Tag
Tags: osint, recon, scanner, bruteforce, web, wireless, social-engineering, c2, privesc, network, credentials, forensics, reversing, cloud, mobile, active-directory, ddos, payload, crawler. To show tools matching a tag:
~/hackingtool/venv/bin/python3 -c "
import sys; sys.path.insert(0, '~/hackingtool')
from hackingtool import _get_all_tags
tag_index = _get_all_tags()
for tool, cat in tag_index.get('TAG_NAME', []):
print(f'{tool.TITLE} [{cat}]')
"5. Get Task Recommendations
Common tasks and recommended tools come from hackingtool._RECOMMENDATIONS. For a task like "scan a network", it maps to tags like scanner, port-scanner. Use _get_all_tags() with those tags to show matching tools.
6. Install a Specific Tool (interactive, hands back to user)
~/hackingtool/venv/bin/python3 -c "
import sys; sys.path.insert(0, '~/hackingtool')
from hackingtool import all_tools, tool_definitions
# Pick category by index (1-based) then tool index
cat_idx = 2 # e.g., Information Gathering
tool_idx = 1 # e.g., nmap
all_tools[cat_idx - 1].TOOLS[tool_idx - 1].install()
"WARNING: Most tool installs will fail on macOS because install() shells out to system package managers (apt, brew). The tool definitions are still useful for discovery — Hermes should suggest the user install the underlying tool directly via Homebrew.
Categories (summary)
| # | Category | Tool Count |
| 1 | 🛡 Anonymously Hiding | 2 |
| 2 | 🔍 Information Gathering | 26 |
| 3 | 📚 Wordlist Generator | 7 |
| 4 | 📶 Wireless Attack | 13 |
| 5 | 🧩 SQL Injection | 7 |
| 6 | 🎣 Phishing Attack | 17 |
| 7 | 🌐 Web Attack | 20 |
| 8 | 🔧 Post Exploitation | 10 |
| 9 | 🕵 Forensic | 8 |
| 10 | 📦 Payload Creation | 8 |
| 11 | 🧰 Exploit Framework | 4 |
| 12 | 🔁 Reverse Engineering | 5 |
| 13 | ⚡ DDOS Attack | 6 |
| 14 | 🖥 Remote Admin (RAT) | 1 |
| 15 | 💥 XSS Attack | 9 |
| 16 | 🖼 Steganography | 4 |
| 17 | 🏢 Active Directory | 6 |
| 18 | ☁ Cloud Security | 4 |
| 19 | 📱 Mobile Security | 3 |
| 20 | ✨ Other Tools | 11 |
| 21 | ♻ Update / Uninstall | 2 |
Workflow for Hermes
- If user asks "what tools for X?", search or use tags to find matches.
- If user asks "list all tools in category Y", programmatically enumerate that category.
- If user asks "install tool Z from hackingtool", explain that hackingtool's install wrappers target Linux (apt/brew), but Hermes can install the tool natively on macOS instead. Offer to find and install via Homebrew.
- If user asks "run hackingtool", remind them to use the
hackingtoolcommand from an interactive terminal (the TUI needs stdin). - If user asks "search hackingtool for KEYWORD", use the programmatic search method above.
Pitfalls
- Never try
hackingtool --helpin a non-TTY — it will hang onPrompt.ask. - Most
install()methods will fail on macOS — accept this gracefully and offer native alternatives. - The TUI is Rich-based and requires TERM env var set.
~/.hackingtool/tools/is where tools WOULD be installed; it's empty by default.- Do NOT use
sudowith hackingtool — the venv install is user-local.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

