output-dev-workflow-cost

Identify Output workflow runs by ID and compute their LLM token and service costs.

430|12|Updated Mar 13, 2026

Search Tags:#workflow #cli #analysis #llm #output #token #cost

Ready to run

npx skills add https://github.com/growthxai/output --skill output-dev-workflow-cost

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: output-dev-workflow-cost
Source: https://github.com/growthxai/output/tree/main/coding_assistants/claude/plugins/outputai/skills/output-dev-workflow-cost
Command: npx skills add https://github.com/growthxai/output --skill output-dev-workflow-cost

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill calculates and presents the cost of a completed Output workflow run, breaking down LLM token usage and external service charges to help you track spending.

Core Features & Use Cases

Per-run cost breakdown: see total cost, token costs, and services for a specific run.
Flexible outputs: view results in text or JSON to integrate into dashboards or reports.
Useful scenarios: cost auditing after batch executions, budgeting for workflows, or vendor demonstrations.

Quick Start

Run the command to retrieve the cost for a known run ID, optionally including a local trace for debugging.

Frequently Asked Questions about output-dev-workflow-cost

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I calculate the cost of an Output workflow run after batch execution?▼

To calculate workflow run cost, you provide the specific run ID to compute associated costs. The tool breaks down LLM token usage and external service charges to audit per-run spend accurately.

Can I get a JSON breakdown of LLM token costs for a specific workflow run?▼

Yes, you can generate machine-readable cost data in JSON format. This output details total cost alongside LLM token costs and external services, suitable for integrating into dashboards or reports.

What do I need to audit per-run spend for an Output CLI workflow?▼

Auditing per-run spend requires the specific run ID of the completed Output workflow. You can also optionally include local trace data to support deeper debugging during the cost analysis process.

How does token usage tracking work for Output workflow cost analysis?▼

Token usage tracking works by analyzing a completed workflow run to break down associated costs. It separates LLM token consumption from external service charges to present a clear per-run spend overview.

What is the best way to track spending and budget for Output workflows?▼

The best way to track spending is computing per-run workflow costs from Output using the run ID. This generates a breakdown of total cost, LLM tokens, and services, which is useful for budgeting workflows or vendor demonstrations.