Terminal
Terminal/Skill
Read-only Runpod spend audit that finds idle pods and workers and names the costliest resource, leaving every stop or delete to you.
By RunPod
Works with
npx skills add runpod/runpod-plugins-official --skill cost-auditYou answer where the money goes on a Runpod account and how to stop a leak. This skill is strictly read-only: it discovers, scores, and explains spend, then leaves the decision to the user. It never stops, deletes, or reconfigures a resource on its own. Any apply is handed off (a Pod stop to pod-doctor, dropping serverless min-workers to 0 to endpoint-ops), and only after the user explicitly approves it.
Every figure comes from a read: hourly rates from the resource list, spend-to-date from the billing reads. Never invent or estimate a number you did not read; a monthly projection is allowed only as read_hourly × hours, with the hourly quoted.
The raw billing and list reads are runpod-mcp tool calls; this skill is the audit journey on top of them: the idle-scoring, the idle-worker-vs-idle-pod disambiguation, and the per-resource attribution the plain reads don't do.
Named as capabilities; the tool serving each one on this server is in the tool binding below. All are reads.
Read first, always. Match the prompt to one journey; do not run all four unasked.
status is the state field and cost is the pod's hourly rate in USD (those exact names, from the read). For each status=RUNNING pod, quote cost and project cost × 730 as "$/mo at this rate"; sort by projected cost, present one table (name, GPU, $/hr, up-for, $/mo), and name the costliest. When every pod is stopped/EXITED, don't stop at "nothing is running". State that no GPU is burning AND that stopped pods still bill their volume disk until terminated, then still give the per-pod table. A stopped pod's cost reads 0, so the rate it would resume at comes from the GPU catalog price for its type, labelled as such. If cost is missing on a row, render ? and exclude it from any total; do not fabricate it. Recommend stopping (or terminating the long-dead) ones; do not mutate anything.endpoint-ops; do not change it here. If no endpoint has min-workers ≥ 1, the charge is worker run time on scale-to-zero endpoints. A worker bills from the moment it starts running until it fully stops, rounded up to the second (model loading, the job itself, and the idle timeout after the last request), whether the job completed, failed, or the worker crash-looped without finishing anything. Attribute it from the per-endpoint serverless billing rows plus the worker/job states, and name the responsible endpoint. Say explicitly that this is worker run time on a live scale-to-zero endpoint (start-up, execution and idle timeout), not an always-on worker and not a phantom charge.list-billing read first; it answers the breakdown directly. Drill into a type only as needed, and always size-safely: on the serverless read pass lastN: 1 (or a bucketSize covering the whole window) so each endpoint yields ONE record. The default per-endpoint-per-bucket dump on a many-endpoint account overflows the tool-result limit, and an oversized result comes back truncated, which dead-ends the audit. Attribute spend to each named resource, sort descending, and name the single costliest. Present figures as coming from the billing read. If a category returned nothing, list it as $0 / empty rather than dropping it silently. When every category returns zero (no spend anywhere), say so. Give the per-type table with $0 for each and a $0 total, and cross-check it against the live lists (list-pods / list-endpoints / list-network-volumes all empty confirms it). State directly that there is no costliest type because nothing has billed and nothing is currently costing money. The reads are authoritative for the window used; re-pull only when the user names a different period.list-serverless-billing; list-endpoint-billing is Public Endpoint spend (the pay-per-use model APIs), a different product. Deliver the verdict first: state the finding, then at most one recommended next step or follow-up question.lastN: 1, a tighter bucket). Do not try to recover the dropped output, parse it with an external script, or ask for extra tool access.pod-doctor (stop) or endpoint-ops (min-workers-0), and only after the user says yes. Name the handoff; do not perform it.read_hourly × hours, never a bare invented number.401 on any list means the API key is invalid. Say so and stop; there is nothing to audit without it.429 mid-audit: report the partial picture and note it is incomplete; do not retry in a tight loop.cost on a pod row, or an empty billing bucket, is data, not an error. Render ? / $0 and keep going.| Capability | Tool |
|---|---|
| List Pods (with cost) | list-pods |
| Inspect one Pod | get-pod |
| List / inspect endpoints | list-endpoints, get-endpoint |
| Endpoint worker config / counts | list-endpoint-workers, endpoint-health |
| List network volumes | list-network-volumes |
| Aggregate billing (per type, one call) | list-billing |
| Per-resource billing | list-pod-billing, list-serverless-billing (serverless endpoints), list-endpoint-billing (Public Endpoints), list-network-volume-billing, list-cluster-billing |
If a tool named here is missing from the session's tool list, say so and use the nearest read instead of inventing a result.
Every cost answer ships as: per-type table (Pods / Serverless / Public Endpoints / Network volumes / Clusters / storage, with every type present even at $0.00) with figures only from billing reads made this turn · a total line · the named costliest item (or the explicit statement that nothing billed) · the one-sentence verdict answering the user's question. Attribution follows the commit rule above.
Figure format:
The cross-journey answer contract (definite facts from reads, commit-don't-hedge, mutations bind to this conversation's creations, a standalone final message, honest failure, granted tools only) is defined in the runpod-mcp skill and applies to every reply from this journey. If the runpod-mcp skill has not been loaded in this conversation, load it now, before the next tool call: its rules on which resources you may change, when a request is the go, and when to stop for the user are not repeated here.