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.
npx agentmods add skills/runpod/runpod-plugins-official/runpod-migratenpx skills add runpod/runpod-plugins-official --skill runpod-migrategit clone --depth 1 https://github.com/runpod/runpod-plugins-officialWrote 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.
[](https://agentmods.dev/skills/runpod/runpod-plugins-official/runpod-migrate)<a href="https://agentmods.dev/skills/runpod/runpod-plugins-official/runpod-migrate"><img src="https://agentmods.dev/badge/skills/runpod/runpod-plugins-official/runpod-migrate.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00092 | $0.04895 |
| Opus 5 | $0.00046 | $0.02448 |
| Sonnet 5 | $0.00018 | $0.00979 |
| Haiku 4.5 | $0.00009 | $0.00490 |
Grade A, and why
runpod-migrate scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Bash(python3:*), Bash(curl:*), Bash(rg:*), Bash(git:*) How it starts
The opening of the file, as written. The whole thing — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate to Runpod REST v2
Moves a codebase off the GraphQL API (api.runpod.io/graphql) and REST v1
(rest.runpod.io/v1) onto REST v2 (api.runpod.io/v2).
The payoff, in one line each — you deliver these to the user at step 6, matched to their actual code. Don't recite them now:
- See stock before you rent —
GET /v2/catalog/gpus?include=AVAILABILITY&product=POD. v1 had no catalog at all, so every capacity retry loop was blind. - Endpoints return their own job URLs —
requestUrls.run, no more string-building. - Real lifecycle states —
PROVISIONING/STARTING/ERRORand anactionslist, so wait-loops fail fast instead of timing out. - Mistakes fail loudly — unknown request fields are rejected by name, with structured errors and honest status codes.
The full set, organized as if their code does X → v2 offers Y: reference/unlocks.md — open it at step 6.
Before you touch any code
Infer the scope, state it, and move — do not open with a questionnaire:
| The user says | Scope |
|---|---|
| "migrate to v2" / nothing specific | all — REST v1 and GraphQL |
| "just the REST stuff", "leave GraphQL alone" | rest — REST v1 only |
| "get us off GraphQL" | graphql — GraphQL only |
The table resolves every phrasing, so scope is not the thing to interrupt for. Say which row you matched and carry on. The question that does need asking comes later — at step 3, when the inventory shows the code depends on a capability v2 removed. That one is a real fork and you cannot answer it for them.
Some things have no v2 equivalent and must stay on GraphQL regardless of scope:
account/billing identity (myself), secrets, spot/interruptible pods, cluster
create/delete. A "full" migration still leaves those calls in place — say so up front
rather than letting the user discover it at the end.
Never rewrite the serverless job API. https://api.runpod.ai/v2/<endpointId>/run,
/runsync, /status, /stream, /cancel is a different API that happens to have
v2 in its path. It is unchanged and out of scope. The inventory reports it separately
so you do not touch it.
What ships with it
10 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.
- evals/availability-and-fallback.eval.md 2.3 KB
- evals/inventory-before-editing.eval.md 1.6 KB
- evals/rest-only-scope.eval.md 1.4 KB
- reference/breaking-changes.md 17 KB
- reference/graphql-to-v2.md 11 KB
- reference/rest-v1-to-v2.md 22 KB
- reference/rollback-flag.md 4.0 KB
- reference/unlocks.md 5.2 KB
- reference/worked-example.md 10 KB
- scripts/rp_api_inventory.py 32 KB runs code
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.
- 5d ago First seen · 361 lines · 92 tokens per session scan A a169392115cf
runpod-migrate is a skill published in the GitHub repository runpod/runpod-plugins-official (44 stars, last pushed 2d ago), licensed Apache-2.0. It adds 92 tokens to every session and 4,895 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…