sandbox-provisioning

Provisions isolated Docker, Fly.io, and VM sandboxes for security testing and exploit development.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/kaminocorp/hermes-alpha-hunter --skill sandbox-provisioning-kaminocorp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sandbox-provisioning
Source: https://github.com/kaminocorp/hermes-alpha-hunter/tree/main/hunter/skills/security/sandbox-provisioning
Command: npx skills add https://github.com/kaminocorp/hermes-alpha-hunter --skill sandbox-provisioning-kaminocorp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security testing and exploit verification require isolated environments that never touch production systems, and manually assembling containers, networks, databases, and testing tools for each engagement is slow and error-prone. ## Core Features & Use Cases - Isolated Environment Provisioning: Spin up Docker networks and containers, Fly.io temporary machines, or VirtualBox VMs with host-only networking for full isolation. - Target Application Deployment: Clone a target repository and auto-detect Node.js, Python, Java, or Dockerized stacks, then build and run the app with matching test databases (PostgreSQL or MySQL) seeded with sample data. - Testing Tool Configuration: Pre-configure Burp Suite project files, SQLMap configs, network capture with tcpdump/ngrep, and Python/Bash exploit templates. - Use Case: During a bug bounty engagement, deploy the target web app into a Docker sandbox, run automated SQL injection and XSS checks against it, capture traffic for analysis, then tear everything down automatically on exit. ## Quick Start Set up an isolated Docker sandbox, deploy the target application from its repository, and run automated vulnerability tests against it.

Frequently Asked Questions about sandbox-provisioning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up an isolated environment for security testing?▼

Create a dedicated Docker network, run the target application and an attacker container (such as Kali Linux) on that network, and keep it separate from production. For full OS access, deploy a temporary Fly.io machine or a VirtualBox VM with host-only networking.

Docker vs VM for exploit development and testing?▼

Docker containers suit application-level testing and quick exploit verification with fast startup. VirtualBox VMs are better for kernel exploits, OS-level testing, and scenarios needing full network isolation through host-only adapters.

How do I deploy a target application from source code for testing?▼

Clone the repository into the sandbox and detect the stack from its manifest files: package.json for Node.js, requirements.txt for Python, pom.xml for Java, or a Dockerfile for containerized apps. Then install dependencies, start the app, and record its listening port.

Can I test SQL injection safely without affecting production?▼

Yes, run SQLMap against the target only inside an isolated sandbox network with a seeded test database containing synthetic data. Confirm the target is within the authorized scope and never point testing tools at production hosts.

How do I clean up temporary sandbox infrastructure after testing?▼

Stop and remove all containers on the sandbox Docker network, delete the network, destroy any Fly.io apps, and archive exploit results to a tarball. Registering a cleanup function with a shell trap ensures teardown runs automatically on exit.