vpn-egress-orchestratorlisted
Install: claude install-skill THEROCKSSS/vpn-egress
# VPN Egress Orchestrator
Running many reachability tasks in parallel over **one shared container**.
The stack tolerates this — it was configured for it — but only under a
specific contract. Break the contract and agents kill each other's runs.
## First: do you actually need subagents?
`check-url.js` takes **any number of URLs in one invocation**, sharing one
browser. Twenty URLs in one call is faster than twenty subagents, uses no
extra context, and produces one already-merged result.
```bash
MSYS_NO_PATHCONV=1 docker exec playwright-vpn \
node /scripts/check-url.js url1 url2 url3 … url20
```
**Fan out only when each target needs real per-target work** — reading a
config to explain *why* one failed, cross-referencing a Caddyfile, chasing a
redirect chain, judging whether a page rendered correctly. That's reasoning
work, which parallelizes. Navigation alone does not.
If the task is "check these N URLs", stop here and use `vpn-egress-testing`.
## The contract
### 1. The parent owns the stack. Always.
Subagents **never** run `docker compose`, `tools/stack.sh up`, or
`tools/stack.sh stop`.
Parallel agents managing one shared stack race: two `up` calls collide, and a
`stop` from the first agent to finish kills every run still in flight —
producing timeouts that look exactly like unreachable sites.
Before dispatching anything:
```bash
cd projects/vpn-egress && bash tools/stack.sh up
MSYS_NO_PATHCONV=1 docker exec playwright-vpn node /scripts/check-ip.js
```
Both mus