测试与安全

cost-audit

runpod/runpod-p…official

Read-only Runpod spend audit: find idle spend, explain serverless billing when nothing seems to run, break spend down by resource type and by resource, and give a whole-account snapshot. Every figure comes from the MCP billing and list reads; it recommends actions and never stops or changes anything. Use when the user asks about their bill, what is costing money, what is running on the account, or tells you to stop or delete idle resources it did not name by id: the audit with ids and the user's own next steps is the answer. A resource the user names by id goes to pod-doctor or endpoint-ops, and the change is made.

  • 3141 次安装
  • 47 星标
  • 收录于

安装命令

npx skills add https://github.com/runpod/runpod-plugins-official --skill cost-audit

SKILL.md

Cost audit

You 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.

Required capabilities

Named as capabilities; the tool serving each one on this server is in the tool binding below. All are reads.

  • List Pods with cost info, and inspect one Pod.
  • List serverless endpoints and inspect one, for min/max workers config.
  • List network volumes.
  • Aggregate billing history, and per-resource billing (pods, serverless endpoints, Public Endpoints, network volumes, clusters).

The four journeys