RunPod pod management

Manage RunPod GPU cloud instances - create, start, stop, connect to pods via SSH and API. Use when working with RunPod infrastructure, GPU instances, or need SSH access to remote GPU machines. Handles pod lifecycle, SSH proxy connections, filesystem mounting, and API queries. Requires runpodctl (brew install runpod/runpodctl/runpodctl).

What to check before installing: 1) This skill expects runpodctl, ssh, sshfs (FUSE) and a RunPod API key — the registry metadata doesn't list those binaries, so make sure you have them and trust runpodctl's source. 2) The mount script will read your SSH private key (from ~/.runpod/ssh/ or a path you set via RUNPOD_SSH_KEY) and write a known_hosts file under ~/.runpod/ssh/; mounting gives the remote root filesystem access to your local mountpoint — only mount pods you trust. 3) The script parses runpodctl output using grep -P (Perl regex); this may be non-portable on some systems (macOS grep may not support -P). 4) Host key handling uses StrictHostKeyChecking=accept-new (it will accept new host keys automatically and store them in the skill’s known_hosts file) — be aware of the security tradeoff. If you’re comfortable with these points and trust RunPod/runpodctl, the skill appears coherent. If unsure, inspect runpodctl and run the mount script in a sandboxed environment first.

Type: OpenClaw Skill Name: runpod Version: 1.0.1 The skill is classified as suspicious due to its use of high-risk capabilities, specifically the `scripts/mount_pod.sh` script. This script utilizes `sshfs` to mount the remote RunPod instance's root filesystem (`root@$IP:/`) locally, which grants extensive file system access. It also handles SSH keys (`IdentityFile`) and uses `StrictHostKeyChecking=accept-new` with a dedicated `known_hosts` file, which, while plausibly needed for managing dynamic cloud environments, represents a significant security capability. There is no clear evidence of intentional malicious behavior, data exfiltration, or prompt injection attempts against the agent; the risky behaviors are aligned with the stated purpose of managing and interacting with RunPod instances.