sume-spend-capped-dogfood

name	sume-spend-capped-dogfood
description	Run paid Sume dogfood QA under an explicit USD cap using idempotency, max_spend_usd where available, cost readback, and no duplicate paid submissions.

Sume Spend-Capped Dogfood

Use this skill when the user authorizes paid Sume QA with a hard budget.

Required Before Paid Calls

• Confirm the exact USD cap.
• Identify the minimum number of jobs needed for evidence.
• Prefer dry-run/admission preview or estimate if exposed by the current tool schema.
• Use stable idempotency keys.
• Use batch state files for more than one job.
• Stop once terminal evidence is sufficient.
• Timeout is not terminal. A paid job remains owned by the agent until it is completed, failed, canceled, or the user explicitly tells you to stop.

If a future release enables MCP paid tools, idempotency_key and max_spend_usd are mandatory. For current CLI commands, record the approved cap in the manifest/report and pass idempotency keys where supported.

Commands

sume doctor --agent --json
sume balance --json
sume tools schema avatar-videos.create --json

Single-job example after explicit approval:

sume avatar-videos create \
  --avatar-handle <ready_avatar_handle> \
  --script "Short QA script." \
  --quality standard \
  --idempotency-key <stable_key> \
  --confirm-paid \
  --agent \
  --json

Then:

sume jobs watch <job_id> --agent --json
sume jobs result <job_id> --agent --json
sume balance --json

If jobs watch times out while the job is still non-terminal, run sume jobs watch <job_id> --timeout-seconds 0 --agent --json, then continue polling or ask whether to keep watching. Do not submit duplicate paid jobs while recovering from timeout or transport failure.

Report

Report requested quality, job id, resource id, expected/reserved/captured/ refunded cost when available, status/result, and whether the cap was respected. If jobs are still non-terminal, say the workflow is still in progress and give the resume/watch command instead of reporting completion. If exact cost telemetry is missing, state that as a product gap instead of inferring a billing guarantee.

Not For

Do not use this skill without an explicit cap. Do not keep spending for broad exploration. Do not print secrets, full URLs, signed URLs, provider payloads, or private identifiers.