What is runpod-usage?

A usage guide for Runpod, a service for renting cloud computers with CPUs or GPUs. It explains pods, serverless endpoints, storage, containers, networking, and the development process for running workloads there.

Use it when selecting GPU or VRAM, building a container, setting up a pod, deploying a serverless endpoint, or planning a repeatable development workflow.

It helps developers choose the right Runpod setup and understand how to provision, prepare, check, and remove cloud workloads without confusing infrastructure concepts.

runpod-usage — Skill for Claude Code by runpod/runpod-plugins-official

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add runpod/runpod-plugins-official --skill runpod-usage

Clone the repo

git clone --depth 1 https://github.com/runpod/runpod-plugins-official

Made for: Claude Code.

Or install runpod, the plugin that ships this one along with the rest of its 16 skills, 1 command, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/runpod/runpod-plugins-official/runpod-usage/github.svg)](https://agentmods.dev/skills/runpod/runpod-plugins-official/runpod-usage)

Your own site

<a href="https://agentmods.dev/skills/runpod/runpod-plugins-official/runpod-usage"><img src="https://agentmods.dev/badge/skills/runpod/runpod-plugins-official/runpod-usage/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/runpod/runpod-plugins-official/runpod-usage"><img src="https://agentmods.dev/badge/skills/runpod/runpod-plugins-official/runpod-usage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 985 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

Socket pass 19 Oct 2026
Snyk pass 19 Oct 2026
NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00065	$0.00985
Opus 5.5	$0.00026	$0.00394
Sonnet 5.5	$0.00013	$0.00197
Haiku 4.5	$0.00006	$0.00098

Measured 2d ago against content hash bd3b755cf3f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

runpod-usage scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/runpod/skills/runpod-usage/SKILL.md · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Runpod usage (concepts)

Background knowledge for making the right choice before you act. This skill runs nothing — once you know what to do, execute with runpod-mcp/runpodctl (infra), flash (your own code), or companion-clis (models/images/data).

This skill explains; the golden paths demonstrate. When the question is really "how do I do X" rather than "how does X work", the verified end-to-end example is the faster answer — runpod/golden-paths/README.md. Read the concept here, then follow the path.

To author files for a custom template, use runpod-build-template; this lane supplies the shared concepts, not a competing packaging workflow.

Read the one reference file that matches the question:

Question	Read
First-run setup / auth — get + set `RUNPOD_API_KEY`, SSH, companion creds	`reference/getting-started.md`
Pods vs serverless, workers, cold starts, FlashBoot, queue vs load-balanced	`reference/concepts.md`
The development loop for ANY workload (start here) — plan → prefer prebuilt → provision → verify → teardown	`reference/development-loop.md`
Stand up / iterate a workload on a pod — the pod sub-loop	`reference/pod-workflows.md`
Deploy / iterate a serverless endpoint — Hub vs flash vs custom, invoke + verify	`reference/endpoint-workflows.md`
Install software on a pod — package hygiene, `uv`, non-interactive, caching	`reference/on-pod-setup.md`
Build a Docker image Runpod can run (handler contract, Dockerfile, `--platform=linux/amd64`)	`reference/docker.md`
How to build an image well — base image, layering, bake-in vs volume, pod vs serverless (queue/LB) contract	`reference/building-images.md`
Where data lives — container disk vs network volume, model caching, S3 access	`reference/storage.md`
Which GPU / how much VRAM / which CUDA version / cost & availability / data centers	`reference/gpu-selection.md`
Why a stopped pod may not restart with a GPU — pods are bound to one machine; what else is per machine	`reference/pods-and-machines.md`
Endpoint releases, rolling updates, version overlap, GitHub builds	`reference/endpoint-builds-and-releases.md`
Storing API tokens and keys as secrets and referencing them from env vars	`reference/secrets.md`
Reaching a pod or endpoint over HTTP (proxy URLs, exposed ports)	`reference/networking.md`
Common mistakes and how to avoid them	`reference/gotchas.md`

Read the full file on GitHub · 66 lines

Files

What ships with it

60 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago Changed · +2 lines · -55 tokens per session bd3b755cf3f7
6d ago Changed fb048c50ed10
7d ago Changed 87629e843917
8d ago Changed e6168287c179
12d ago Changed cc724687c8cb
13d ago Changed · +21 lines 7b404797d21c
15d ago Changed e8009cbaf74c
23d ago Changed 47fbb38f2c86
1mo ago First seen · 43 lines · 120 tokens per session scan A 6a1b7763f20c

Subscribe to this mod's changes

runpod-usage is a skill published in the GitHub repository runpod/runpod-plugins-official (46 stars, last pushed today), licensed Apache-2.0. It adds 65 tokens to every session and 985 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude Code Cloud Containers DevOps and cloud GPU agent-skills ai-agents codex cursor

dokploy-deploy

This skill should be used when user asks to "deploy with Dokploy", "use Dokploy Cloud", "manage self-hosted Dokploy", "deploy Docker Compose on Dokploy", "manage Dokploy databases", "configure Dokploy domains", or "look up Dokploy CLI commands".

fcakyon/claude-codex-settings · 63 tokens

nvcf-self-managed-prerequisite

Install the prerequisites the NVCA operator / compute plane needs before nvcf-nvca-install can succeed: the operator tool nvcf-cli (required by the compute-plane stack's register-cluster step), KAI Scheduler (for the KAIScheduler feature gate), and the SMB CSI driver (for the sharedStorage Samba sidecar PVCs). The two…

NVIDIA/nvcf · 195 tokens

nvca-self-managed-install

Install or validate the NVCA Operator chart against a self-managed NVCF control plane from the native monorepo. Use when the control plane comes from deploy/stacks/self-managed and NVCA must be installed with stack-derived image repository settings.

NVIDIA/nvcf · 55 tokens

qdrant-deployment-options

Guides Qdrant deployment selection. Use when someone asks 'how to deploy Qdrant', 'Docker vs Cloud', 'local mode', 'embedded Qdrant', 'Qdrant EDGE', 'which deployment option', 'self-hosted vs cloud', or 'need lowest latency deployment'. Also use when choosing between deployment types for a new project.

qdrant/skills · 79 tokens

cometchat-self-host

Run CometChat on your own infrastructure — when to self-host, the deployment models (Docker Swarm, Kubernetes, air-gapped), sizing & prerequisites, and how to point your app at the self-hosted instance. CometChat's enterprise differentiator: full data sovereignty. Triggers: 'self-host cometchat', 'on-prem cometchat'…

cometchat/cometchat-skills · 124 tokens

mirrord-operator

Help users install and configure the mirrord Operator for team/enterprise environments. Use when users ask about operator setup, Helm installation, cloud API key or license configuration, air-gapped/offline licensing, enabling features (queue splitting, DB branching, preview environments, multi-cluster), internal…

metalbear-co/skills · 124 tokens