Workflow Cost Audit with Claude Code: Result JSON Schema

A production playbook for workflow cost audit in cross-industry operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.

Audience: Founders and infra owners

The problem

Founders and infra owners need workflow cost audit to run repeatedly against run logs, token usage, sandbox minutes, and artifact storage records. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.

Implementation path

Define the outer result contract once, let the workflow cost audit skill own body.data, and reject terminal output that does not match the expected schema.

Tradeoffs and failure modes

Schema enforcement adds upfront design work, but removes prompt parsing from the product surface. For workflow cost audit, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.

Result shape

{
  "schema_version": "argo.result.v1",
  "summary": "workflow cost audit completed",
  "body": { "type": "workflow_cost_audit", "data": {}, "exceptions": [] },
  "artifacts": []
}

Run this on Argo