hackingBuddyGPT
Copilot instructions1.3k starsChanged 3 months agoMITView on GitHub
hackingBuddyGPT is a research-driven Python framework that helps security researchers and penetration testers use Large Language Models (LLMs) to automate and experiment with security testing, especially privilege escalation and web/API pentesting. It supports both local shell and SSH connections to targets, and is designed for rapid prototyping of new agent-based use cases. Warning: This tool executes real commands on live systems—use only in safe, isolated environments.
- Reads credentials
- Installs packages
We split this copilot-instructions.md into the rules it gives an agent
10 rules. About 0 are common, 4 are distinctive, and 6 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.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Python: Use 3.10+ (see pyproject.toml).
- Very specific: line 41
Follow PEP8 and use ruff for linting (see [tool.ruff] in pyproject.toml).
- Distinctive: line 42
Use type hints and docstrings for all public functions/classes.
- Very specific: line 43
Place new agent logic in usecases/, new capabilities in capabilities/.
- Distinctive: line 44
Prefer composition (capabilities, helpers) over inheritance.
- Very specific: line 45
Use the logging utilities in utils/logging.py.
- Very specific: line 46
Document all new scripts and major changes in the README.md or relevant .md files.
- Distinctive: line 59
Use virtual environments for Python dependencies.
- Distinctive: line 60
Never expose the web viewer to the public internet.
- Very specific: line 61
Always set API keys and credentials in .env or as prompted by scripts.
≈ “Common” is an estimate: at least 1 in 5 of the 3,669 Copilot instructions 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
Copilot Instructions for hackingBuddyGPT
Project Summary
hackingBuddyGPT is a research-driven Python framework that helps security researchers and penetration testers use Large Language Models (LLMs) to automate and experiment with security testing, especially privilege escalation and web/API pentesting. It supports both local shell and SSH connections to targets, and is designed for rapid prototyping of new agent-based use cases. Warning: This tool executes real commands on live systems—use only in safe, isolated environments.
Tech Stack
- Language: Python 3.10+
- Core dependencies: See
pyproject.toml(notable:fabric,requests,pydantic,pytest) - CLI Entrypoint:
wintermute(seesrc/hackingBuddyGPT/cli/wintermute.py) - Web viewer: Optional, for log viewing (
wintermute Viewer) - RAG/Knowledge base: Markdown files in
rag/
Project Structure
src/hackingBuddyGPT/— Main Python packagecli/— CLI entrypoint (wintermute.py)capabilities/— Modular agent actions (e.g., SSH, HTTP, note-taking)usecases/— Agent logic for each use case (Linux privesc, web, API, etc.)utils/— Shared helpers (LLM, logging, config, prompt generation)
tests/— Pytest-based unit and integration testsrag/— Markdown knowledge base for RAG (GTFOBins, HackTricks)docs/— Minimal, see https://docs.hackingbuddy.ai for full docs
Setup & Usage
- Python: Use 3.10+ (see
pyproject.toml). - Install:
python -m venv venv source venv/bin/activate pip install -e . - Run:
- List use cases:
python src/hackingBuddyGPT/cli/wintermute.py - Example:
python src/hackingBuddyGPT/cli/wintermute.py PrivEscLinux --llm.api_key=... --conn=ssh ... - See
README.mdfor setup and usage instructions.
- List use cases:
- Testing:
pip install '.[testing]' && pytest - Linting:
ruff(config inpyproject.toml) - Benchmark:
uv run benchmark_privesc.py --helpruns privesc use-cases against localprivesc_*Docker containers.
Coding Guidelines
- Follow PEP8 and use
rufffor linting (see[tool.ruff]inpyproject.toml). - Use type hints and docstrings for all public functions/classes.
- Place new agent logic in
usecases/, new capabilities incapabilities/. - Prefer composition (capabilities, helpers) over inheritance.
- Use the logging utilities in
utils/logging.py. - Document all new scripts and major changes in the
README.mdor relevant.mdfiles. - Mark all workarounds or hacks with
HACK,TODO, orFIXME.
Existing Tools & Resources
- Documentation: https://docs.hackingbuddy.ai
- Community/Support: Discord link in
README.md - Security Policy: See
SECURITY.md - Code of Conduct: See
CODE_OF_CONDUCT.md - Contribution Guide: See
CONTRIBUTING.md - Citations: See
CITATION.cff - Benchmarks: https://github.com/ipa-lab/benchmark-privesc-linux
Tips to Minimize Bash/Build Failures
- Use virtual environments for Python dependencies.
- Never expose the web viewer to the public internet.
- Always set API keys and credentials in
.envor as prompted by scripts. - For RAG, add new markdown files to the appropriate
rag/subfolder.
For further details, see the README.md and https://docs.hackingbuddy.ai. When in doubt, prefer existing patterns over inventing new ones.
Trending
More talk lately.thin dataabout the whole repository
Who's talking about ipa-lab/hackingBuddyGPT
- lloydchang/ipa-lab-hackingBuddyGPT“docs(CODESPACES.md): clarify”GitHub · Dec 5, 2024 · 1 reactions
- lloydchang/ipa-lab-hackingBuddyGPT“docs(CODESPACES.md): add gemini”GitHub · Dec 5, 2024 · 1 reactions
- lloydchang/ipa-lab-hackingBuddyGPT“docs(README.md): alphabetize”GitHub · Dec 5, 2024 · 1 reactions
- lloydchang/ipa-lab-hackingBuddyGPT“docs: Move Codespaces documentation to CODESPACES.md”GitHub · Dec 5, 2024 · 1 reactions
- djmahe4/cyber-tools-index“[WIP] Update tools_config.json with AI security tools from Medium list”GitHub · Oct 2, 2026
The biggest 5 of 8 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 8
Talked about on GitHub (8 times).
On GitHub · 8
- Dec 5, 2024docs(CODESPACES.md): clarify — lloydchang/ipa-lab-hackingBuddyGPT1 reaction · 1 comment
- Dec 5, 2024docs(CODESPACES.md): add gemini — lloydchang/ipa-lab-hackingBuddyGPT1 reaction · 1 comment
- Dec 5, 2024docs(README.md): alphabetize — lloydchang/ipa-lab-hackingBuddyGPT1 reaction · 1 comment
- Dec 5, 2024docs: Move Codespaces documentation to CODESPACES.md — lloydchang/ipa-lab-hackingBuddyGPT1 reaction · 1 comment
- Oct 2, 2026[WIP] Update tools_config.json with AI security tools from Medium list — djmahe4/cyber-tools-index0 reactions
3 more on GitHub
- Aug 6, 2024I am studying Computer Science with a Cybersecurity emphasis — uzmahamid01/uzmahamid010 reactions
- Aug 5, 2024Currently pursing my master in Computer Science, looking for any opportunities to venture into cybersecurity. — toluwalopeoolagbegi/landing_page0 reactions
- Aug 5, 2024I have a passion for software development, artificial intelligence, and cybersecurity. — princesssopeju/Landing-Page0 reactions
Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.
Of the Copilot instructions files we read, the 2,297 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

