Overview
Period: 2026-05-27 to 2026-05-28
Runs analyzed: 8 (5 had token data)
Total tokens: 3,763,650 across all workflows
Estimated total cost: $0.77
Total Actions minutes: 28 min
Workflow Summary
| Workflow |
Runs |
Total Tokens |
Avg Tokens/Run |
Total Cost |
Avg Cost/Run |
Total Turns |
Avg Turns/Run |
| Documentation Maintainer |
1 |
2,410K |
2,410K |
$0.39 |
$0.39 |
31 |
31 |
| Smoke Claude |
4 |
1,353K |
338K |
$0.38 |
$0.10 |
22 |
5.5 |
| Security Guard |
3 |
— |
— |
— |
— |
— |
— |
🔍 Optimization Opportunities
-
Documentation Maintainer — $0.39/run, 31 turns, 2.4M tokens in a single run
- High turn count (31) suggests significant back-and-forth; consider pre-computing deterministic steps in separate workflow steps before handing off to the agent
- At 2.4M tokens/run this is the single largest cost driver — review whether the system prompt or context window is unnecessarily large
- No
token_usage_summary available; enabling detailed tracking would surface cache hit/miss rates
-
Security Guard — 3 runs with no token data
- All 3 Security Guard runs are missing
token_usage — the api-proxy may not be enabled for this workflow
- Recommend enabling
--enable-api-proxy to gain cost visibility
Per-Workflow Details
Documentation Maintainer
- Runs: 1 — 26557520246
- Total tokens: 2,410,409 (avg 2,410K/run)
- Effective tokens: 9,726,361 (effective multiplier: ~4x — likely cache writes dominating)
- Estimated cost: $0.39 (avg $0.39/run)
- Turns: 31 total (avg 31/run)
- Action minutes: 6 min
- Cache analysis: No
token_usage_summary available
- Error rate: 0/1 runs
Smoke Claude
- Runs: 4
- Total tokens: 1,353,241 (avg 338K/run)
- Estimated cost: $0.38 (avg $0.10/run)
- Turns: 22 total (avg 5.5/run)
- Action minutes: 14 min
- Cache analysis: No
token_usage_summary available
- Error rate: 0/4 runs
Security Guard
- Runs: 3
- Token data: ❌ Missing for all runs
- Action minutes: 8 min
- Error rate: 0/3 runs
Workflows Without Token Data
Runs where token_usage was null or 0 — these may not have the api-proxy enabled:
| Workflow |
Runs Missing Data |
Example Run |
| Security Guard |
3/3 |
26520287224 |
To instrument these workflows, add --enable-api-proxy to the awf invocation and ensure token_usage_summary reporting is wired up.
Historical Trend
This appears to be among the first Claude token usage reports — no earlier reports with the claude-token-usage-report label were found for comparison.
References: §26566625741
Generated by Daily Claude Token Usage Analyzer · sonnet46 773.2K · ◷
Overview
Period: 2026-05-27 to 2026-05-28
Runs analyzed: 8 (5 had token data)
Total tokens: 3,763,650 across all workflows
Estimated total cost: $0.77
Total Actions minutes: 28 min
Workflow Summary
🔍 Optimization Opportunities
Documentation Maintainer — $0.39/run, 31 turns, 2.4M tokens in a single run
token_usage_summaryavailable; enabling detailed tracking would surface cache hit/miss ratesSecurity Guard — 3 runs with no token data
token_usage— the api-proxy may not be enabled for this workflow--enable-api-proxyto gain cost visibilityPer-Workflow Details
Documentation Maintainer
token_usage_summaryavailableSmoke Claude
token_usage_summaryavailableSecurity Guard
Workflows Without Token Data
Runs where
token_usagewas null or 0 — these may not have the api-proxy enabled:To instrument these workflows, add
--enable-api-proxyto theawfinvocation and ensuretoken_usage_summaryreporting is wired up.Historical Trend
This appears to be among the first Claude token usage reports — no earlier reports with the
claude-token-usage-reportlabel were found for comparison.References: §26566625741