mcpField
H
hackthebox

hackthebox

github.com/transilienceaiSecurity598198 installsUpdated 13w ago
Repository

About hackthebox

A security workflow skill for Hack The Box competitions and challenges. It guides setup, platform access, per-target agent coordination, and post-solve reporting and notifications.

Key features

  1. 01Competition credentials and platform login
  2. 02Machine VPN and connectivity checks
  3. 03Per-challenge workspace setup
  4. 04Coordinator agent spawning per target
  5. 05Post-solve skill updates and Slack notifications

Use cases

  1. 01Prepare an environment for a Hack The Box machine challenge
  2. 02Coordinate agents across multiple targets
  3. 03Organize challenge results and send completion notices

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/transilienceai/communitytools --skill hackthebox

After installing, type/hacktheboxin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

reference/
logging-spec.md
platform-navigation.md
slack-notifications.md
vpn-pool-routing.md
vpn-setup.md
workflow.md

Details

From the project README

Workflow

  • workflow.md — Complete workflow with commands. Read this for each step
Steps
  1. Get Credentials — python3 .claude/tools/env-reader.py HTB_USER HTB_PASS HTB_TOKEN ANTHROPIC_API_KEY SLACK_BOT_TOKEN HTB_SLACK_CHANNEL_ID
  2. Only for "Machine" kind of competition -> Verify vpn is running, otherwise download the vpn file from the platform and instruct the user on how to enable it
  3. Generate output dirs — mkdir -p YYMMDD_<name>/{recon,findings,logs,artifacts,tools,reports} for each challenge. Do not seed attack-chain.md or experiments.md from the orchestrator — those are the coordinator subagent's first action (see skills/coordination/reference/spawning-recipes.md).
  4. To achieve the tasks given by the user, when possible use the HTB_TOKEN, otherwise login to the platform using playwright at https://account.hackthebox.com/login and fill the login form with the HTB_USER and HTB_PASS
  5. If necessary, start the machines
  6. If necessary, check network connectivity to the machines
  7. Spawn coordinator subagent per target — Agent(name="coordinator-{tag}", run_in_background=True, ...) per spawning-recipes.md. Never run the P0-P6 coordinator workflow inline in the orchestrator session — the bookkeeping discipline (attack-chain.md, experiments.md, goal_attempts counting, mandatory skeptic at experiments 5/15/25) requires the subagent boundary. Max N concurrent agents, queue-based spawning.
  8. Post-solve Phase 3 — parent orchestrator (not coordinator) always runs /skill-update + Slack after each coordinator returns its PHASE3_SUMMARY (see workflow.md step 8)

References

Comments

Markdown supported