agentleFS
ariana-dot-devariana-dot-dev/cloud-sandbox-vm-skills/skills/parallel-agents/SKILL.md

parallel-agents

Skill2 starsChanged 5 months agoMITView on GitHub

Build an "agent factory" — configure one cloud VM once, then disk-level fork it into a fleet of identical isolated machines so many agents run in parallel, each with its own filesystem, IPv4, and SSH. Flat per-second pricing makes a fleet ~10x cheaper than E2B/Modal (50 VMs ≈ $432/mo vs ~$4k). Use to fan work across many real machines instead of threads.

  • Pipes a download into a shell
  • Reads credentials

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use nextjs-react-expert, intelligent-routing and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SKB3002Skill

    nextjs-react-expert

    React and Next.js performance optimization from Vercel Engineering. Use when building React components, optimizing performance, eliminating waterfalls, reducing bundle size, reviewing code for performance issues, or implementing server/client-side optimizations.

    Also in 3 projects that use this

  • SKB3002Skill

    intelligent-routing

    Automatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions.

    Also in 3 projects that use this

  • xfstudioSkill

    rust-pro

    Master Rust 1.75+ with modern async patterns, advanced type system

    Also in 3 projects that use this

  • VercelSkill

    web-design-guidelines

    Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Keep setup.sh and the start command idempotent so every fork bootstraps reliably.

    line 36

“Common” is measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “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
SKILL.md

Parallel agents / agent factory (Box)

Use this when work should be fanned out across many isolated environments: N agents on N tasks, a config sweep, or sharding a workload — and each worker needs a real machine, not a coroutine. Box move: configure one box (clone, install, secrets), then fork it; each fork is an independent VM from that snapshot, so you skip re-provisioning every machine.

Why Box

  • Fork = a configured template — one setup, N identical machines (disk-level, no re-clone per VM).
  • True isolation per agent — separate filesystem, dedicated IPv4, SSH; agents can even talk over the network.
  • Fleet economics — 50 VMs × 240 h/mo ≈ $432 (Box) vs ~$4,124 (E2B) / ~$7,160 (Modal).

Honest scoping

Box forks at the disk level, not memory — a fork does not keep the parent's running processes; re-run your start command after fork. For running-process fork or routinely 1000+ concurrent VMs with <500 ms boot, E2B/Modal are built for that. Box's sweet spot: tens of persistent, cheap, fully-isolated machines. EU-only; 100 active VMs soft cap (raising).

Prereqs

curl -fsSL https://box.ascii.dev/install | sh, then box login "$BOX_API_KEY" --json.

Recipe

base="$(box new --json | jq -r 'select(.event == "ready") | .id')"
box ssh "$base" -- bash -s < ./setup.sh                 # configure once
for i in $(seq 1 10); do
  fork="$(box fork "$base" --json | jq -r 'select(.event == "ready") | .id')"
  box ssh "$fork" -- "cd /project && ./run-task.sh $i" &
done
wait

Keep setup.sh and the start command idempotent so every fork bootstraps reliably.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.