agentleFS
ipa-labipa-lab/hackingBuddyGPT/.github/copilot-instructions.md

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
  1. Very specific:

    Python: Use 3.10+ (see pyproject.toml).

    line 25
  2. Very specific:

    Follow PEP8 and use ruff for linting (see [tool.ruff] in pyproject.toml).

    line 41
  3. Distinctive:

    Use type hints and docstrings for all public functions/classes.

    line 42
  4. Very specific:

    Place new agent logic in usecases/, new capabilities in capabilities/.

    line 43
  5. Distinctive:

    Prefer composition (capabilities, helpers) over inheritance.

    line 44
  6. Very specific:

    Use the logging utilities in utils/logging.py.

    line 45
  7. Very specific:

    Document all new scripts and major changes in the README.md or relevant .md files.

    line 46
  8. Distinctive:

    Use virtual environments for Python dependencies.

    line 59
  9. Distinctive:

    Never expose the web viewer to the public internet.

    line 60
  10. Very specific:

    Always set API keys and credentials in .env or as prompted by scripts.

    line 61

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
copilot-instructions.md

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 (see src/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 package
    • cli/ — 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 tests
  • rag/ — 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.md for setup and usage instructions.
  • Testing: pip install '.[testing]' && pytest
  • Linting: ruff (config in pyproject.toml)
  • Benchmark: uv run benchmark_privesc.py --help runs privesc use-cases against local privesc_* Docker containers.

Coding Guidelines

  • Follow PEP8 and use ruff for linting (see [tool.ruff] in pyproject.toml).
  • Use type hints and docstrings for all public functions/classes.
  • Place new agent logic in usecases/, new capabilities in capabilities/.
  • Prefer composition (capabilities, helpers) over inheritance.
  • Use the logging utilities in utils/logging.py.
  • Document all new scripts and major changes in the README.md or relevant .md files.
  • Mark all workarounds or hacks with HACK, TODO, or FIXME.

Existing Tools & Resources

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 .env or 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.

Download now (ZIP)

Trending

More talk lately.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 1 mentionNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the ipa-lab/hackingBuddyGPT repository that our weekly crawl found: only 8 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Who's talking about ipa-lab/hackingBuddyGPT

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

3 more on GitHub
  • 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.