Multi-Agent Sandbox

Setup multi-agent sandbox infrastructure with Docker, Discord, SSH, and Tailscale. Use when: (1) creating a sandboxed agent for cross-gateway collaboration,...

This skill appears to do what it says, but it requires you to make host‑level, persistent changes (systemd services, firewall rules, network bridges) and to give sandbox agents many powerful capabilities (exec/process, sessions_send). Before installing: (1) only run this on a dedicated host or VM you control; do not use your main agent host; (2) restrict socat binds to the smallest necessary IPs and verify the exact unit files before enabling them; (3) use per‑agent Discord bot tokens with minimal scopes and do not reuse main agent credentials; (4) limit sandbox tool allowlists — remove exec/process or reduce workspace access if possible; (5) use Tailscale ACLs/exit node settings to restrict routes and audit connections; (6) rebuild and inspect the sandbox Docker image locally (avoid pulling unvetted images); and (7) log and monitor the created services and network flows so you can quickly revoke access. If you are unsure about any host commands or the source of this skill, ask the author for justification, a threat model, or a reviewed implementation before proceeding.

Type: OpenClaw Skill Name: multi-agent-sandbox Version: 1.0.0 The skill bundle provides a detailed architectural guide and configuration templates for setting up a multi-agent sandbox environment using Docker, Discord, and Tailscale. The instructions in SKILL.md focus on legitimate infrastructure setup, including socat-based networking bridges to allow sandboxed containers to access a shared VPS via the host's Tailscale connection. The provided agent configurations include proactive security measures such as read-only root filesystems and explicit tool allowlists/denylists, showing no signs of malicious intent or data exfiltration.