القائمة
Manage Vers VMs (vers.sh) - create, branch, commit, restore, pause/resume Firecracker VMs. Use when working with Vers platform, VM orchestration, or when you need isolated execution environments.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Bootstrap a self-improving agent fleet on Vers from scratch. Walks through deploying agent-services, building a golden image, testing the loop, and running first tasks. Use when onboarding someone new to the Vers agent fleet workflow.
Bootstrap a Vers VM into a golden image with punkin-pi, Node.js, dev tools, and swarm extensions installed. Creates a committed snapshot that can be branched for self-organizing agent swarms.
How Vers VM networking works — public URLs, port routing, TLS proxy, IPv6, and running services on VMs.
Contribute a bug fix or improvement to pi-v. Use when you've found and fixed an issue in the pi-v package.
Orchestrate agent swarms across Vers VMs - spawn parallel agents on branched VMs for distributed work, parallel exploration, or multi-path problem solving. Use when you need to run multiple agents simultaneously on isolated environments.
Deep investigation of Vers platform issues (API, orchestrator, agent, docs). Use when encountering any Vers platform problem that needs thorough debugging and issue reporting.
| name | vers-vm |
| description | Manage Vers VMs (vers.sh) - create, branch, commit, restore, pause/resume Firecracker VMs. Use when working with Vers platform, VM orchestration, or when you need isolated execution environments. |
Vers provides Firecracker VMs that can be branched like git. Use for isolated environments, parallel exploration, or safe experimentation.
VERS_API_KEY environment variable sethttps://api.vers.sh/api/v1curl -s -H "Authorization: Bearer $VERS_API_KEY" \
https://api.vers.sh/api/v1/vms | jq .
curl -s -X POST -H "Authorization: Bearer $VERS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"vm_config": {"vcpu_count": 1, "mem_size_mib": 512, "fs_size_mib": 512}}' \
https://api.vers.sh/api/v1/vm/new_root | jq .
Add ?wait_boot=true to wait for VM to be ready.
curl -s -X POST -H "Authorization: Bearer $VERS_API_KEY" \
https://api.vers.sh/api/v1/vm/{vm_id}/branch | jq .
curl -s -X POST -H "Authorization: Bearer $VERS_API_KEY" \
https://api.vers.sh/api/v1/vm/{vm_id}/commit | jq .
Returns commit_id for later restore.
curl -s -X POST -H "Authorization: Bearer $VERS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"commit_id": "COMMIT_ID"}' \
https://api.vers.sh/api/v1/vm/from_commit | jq .
# Pause
curl -s -X PATCH -H "Authorization: Bearer $VERS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"state": "Paused"}' \
https://api.vers.sh/api/v1/vm/{vm_id}/state
# Resume
curl -s -X PATCH -H "Authorization: Bearer $VERS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"state": "Running"}' \
https://api.vers.sh/api/v1/vm/{vm_id}/state
curl -s -X DELETE -H "Authorization: Bearer $VERS_API_KEY" \
https://api.vers.sh/api/v1/vm/{vm_id}
curl -s -H "Authorization: Bearer $VERS_API_KEY" \
https://api.vers.sh/api/v1/vm/{vm_id}/ssh_key | jq .
Returns ssh_private_key and ssh_port (443).
Vers uses SSH-over-TLS on port 443:
# Save the key
curl -s -H "Authorization: Bearer $VERS_API_KEY" \
https://api.vers.sh/api/v1/vm/{vm_id}/ssh_key | jq -r .ssh_private_key > /tmp/vers-key.pem
chmod 600 /tmp/vers-key.pem
# Connect via SSH-over-TLS
ssh -i /tmp/vers-key.pem \
-o StrictHostKeyChecking=no \
-o UserKnownHostsFile=/dev/null \
-o ProxyCommand="openssl s_client -connect %h:443 -servername %h -quiet 2>/dev/null" \
root@{vm_id}.vm.vers.sh
commit → save commit_idbooting — VM is starting uprunning — VM is active and accessiblepaused — VM is suspended (no compute cost, state preserved)