Overview
Period: 2026-04-30T23:26Z to 2026-05-01T17:28Z
Runs analyzed: 42 (35 had token data; 7 had 0 tokens due to early failures)
Total tokens: 7,847K (effective: 2,419K with caching)
Estimated total cost: $6.14
Total Actions minutes: 201 min
⚠️ 7 runs had no token data (3× Security Guard, 4× Smoke Claude) — early failures before the agent started.
Workflow Summary
| Workflow |
Runs |
Total Tokens |
Avg Tokens/Run |
Total Cost |
Avg Cost/Run |
Avg Turns |
| Security Guard |
20 |
5,168K |
258K |
$4.98 |
$0.25 |
6.6 |
| Smoke Claude |
22 |
2,679K |
122K |
$1.16 |
$0.05 |
5.2 |
🔍 Optimization Opportunities
-
Security Guard — $0.25/run avg, high token count, elevated error rate ⚠️
- High avg tokens (258K/run, threshold 100K): claude-sonnet-4-6 is handling extensive code analysis; consider whether all review passes are necessary or can be parallelized/cached in deterministic pre-steps
- High error rate: 8/20 runs (40%) had errors — above the 30% threshold; investigate reliability issues
- Rising cost trend: +32% avg cost/run vs previous report ($0.19 → $0.25) — exceeds 20% increase threshold
- Some runs reached 17–18 turns (threshold: 15); the highest-cost run ($0.61, 17 turns) suggests the agent is doing significant back-and-forth
- Cache efficiency is 86.1% (healthy) on claude-sonnet-4-6 — caching is working well; the cost is driven by volume
-
Smoke Claude — cost stable and low at $0.05/run ✅
- Uses claude-haiku exclusively — appropriate model choice
- Cache efficiency 75.2% — reasonable for short smoke test conversations
- 5/22 runs had errors or missing data (23%, below threshold)
- No action needed
Per-Workflow Details
Security Guard
- Runs: 20 (links below)
- Total tokens: 5,168K (avg 258K/run)
- Estimated cost: $4.98 (avg $0.25/run)
- Turns: 132 total (avg 6.6/run)
- Actions minutes: 103
- Model breakdown: claude-sonnet-4-6 (primary: 96 requests, 4.4M cache read, 706K cache write) + claude-haiku-4-5-20251001 (12 requests, orchestration)
- Cache analysis: cache_read=4,377K, cache_write=706K, efficiency=86.1% — writes are well-reused
- Error rate: 8/20 runs (40%) ⚠️
Smoke Claude
- Runs: 22
- Total tokens: 2,679K (avg 122K/run)
- Estimated cost: $1.16 (avg $0.05/run)
- Turns: 114 total (avg 5.2/run)
- Actions minutes: 98
- Model breakdown: claude-haiku-4-5-20251001 exclusively (80 requests)
- Cache analysis: cache_read=1,996K, cache_write=660K, efficiency=75.2%
- Error rate: 5/22 runs with errors or no data (23%)
Runs Without Token Data
These 7 runs had token_usage = 0 — agent likely didn't start due to infrastructure or pre-agent failures:
Historical Trend
Compared to previous report (#2325 — 2026-04-30):
| Workflow |
Prev Avg Cost |
Curr Avg Cost |
Change |
| Security Guard |
$0.19/run |
$0.25/run |
+32% ⚠️ |
| Smoke Claude |
$0.06/run |
$0.05/run |
-17% ✅ |
Security Guard crossed the +20% increase threshold. The increase is driven by more PRs with larger diffs being reviewed — the recent copilot/optimize-api-proxy-efficiency PR branch contributed several high-turn runs. Cache efficiency remains excellent, so the cost growth reflects genuine workload increase rather than caching regression.
Previous Report
#2325 — 2026-04-30
References:
Generated by Daily Claude Token Usage Analyzer · ● 395.8K · ◷
Overview
Period: 2026-04-30T23:26Z to 2026-05-01T17:28Z
Runs analyzed: 42 (35 had token data; 7 had 0 tokens due to early failures)
Total tokens: 7,847K (effective: 2,419K with caching)
Estimated total cost: $6.14
Total Actions minutes: 201 min
Workflow Summary
🔍 Optimization Opportunities
Security Guard — $0.25/run avg, high token count, elevated error rate⚠️
Smoke Claude — cost stable and low at $0.05/run ✅
Per-Workflow Details
Security Guard
Smoke Claude
Runs Without Token Data
These 7 runs had
token_usage = 0— agent likely didn't start due to infrastructure or pre-agent failures:Historical Trend
Compared to previous report (#2325 — 2026-04-30):
Security Guard crossed the +20% increase threshold. The increase is driven by more PRs with larger diffs being reviewed — the recent
copilot/optimize-api-proxy-efficiencyPR branch contributed several high-turn runs. Cache efficiency remains excellent, so the cost growth reflects genuine workload increase rather than caching regression.Previous Report
#2325 — 2026-04-30
References: