📊 Claude Token Usage Report2026-07-02

[github-actions]

Overview

Period: 2026-07-01 to 2026-07-02 (last 24 hours)
Runs analyzed: 18 (0 had API token data — see note below)
Workflow: Smoke Claude (only Claude-engine workflow active in this period)
Total AIC (Agent Inference Credits): 660.24
Total Actions minutes: 82 min across 18 runs
Success rate: 16/18 (89%) — 2 failures with 4 total errors

⚠️ No API token instrumentation data available. All token_usage and estimated_cost fields are null for every run. This indicates the --enable-api-proxy sidecar is either not enabled for this workflow or token tracking is not configured. AIC (Agent Inference Credits) and Actions minutes are reported as proxies.

Workflow Summary

Workflow	Runs	Success	Fail	Total AIC	Avg AIC/Run	Actions Min	Avg Min/Run	Errors
Smoke Claude	18	16	2	660.24	36.68	82	4.6	4

🔍 Optimization Opportunities

1. Smoke Claude — 22% error rate (4 errors across 18 runs), approaching the 30% reliability threshold

   • 2 runs failed outright with no AIC recorded (runs §28550453263 and §28540470721)
   • Recommend investigating failure patterns to improve reliability before error rate crosses 30%

2. Bimodal AIC distribution — runs cluster into two groups (~30 AIC and ~52–54 AIC)

   • 7 runs averaged ~30.1 AIC (lighter execution path, ~4 min)
   • 9 runs averaged ~52.4 AIC (heavier execution path, ~5–6 min)
   • Consider profiling what triggers the heavier path; if it's redundant work, pre-computing in steps could reduce ~42% of AIC spend on those runs

3. No token telemetry — token_usage, estimated_cost, and turns are all null

   • Enable --enable-api-proxy in the Smoke Claude workflow to capture per-turn token breakdowns, prompt cache hit rates, and USD cost estimates
   • Without this data, it's impossible to track cache efficiency or model-level costs

Per-Workflow Details

Smoke Claude

• Workflow path: .github/workflows/smoke-claude.lock.yml
• Runs: 18 total
• Total AIC: 660.24 (avg 36.68/run)
• Total Actions minutes: 82 (avg 4.6 min/run)
• Success: 16/18 — Failure: 2/18
• Errors: 4 total (22% of runs)
• Token data: None (api-proxy not instrumented)

Run	Date (UTC)	Result	AIC	Actions Min
§28558786426	2026-07-02 01:22	✅ success	49.97	6
§28552986195	2026-07-01 22:51	✅ success	54.43	6
§28550453263	2026-07-01 21:58	❌ failure	—	4
§28543660205	2026-07-01 19:50	✅ success	30.18	4
§28543463492	2026-07-01 19:46	✅ success	30.20	5
§28543418445	2026-07-01 19:46	✅ success	52.25	4
§28542878667	2026-07-01 19:36	✅ success	52.23	4
§28542131887	2026-07-01 19:23	✅ success	30.16	4
§28542032285	2026-07-01 19:21	✅ success	30.11	5
§28541983476	2026-07-01 19:20	✅ success	30.11	4
§28541927832	2026-07-01 19:19	✅ success	30.10	5
§28541883824	2026-07-01 19:18	✅ success	30.14	5
§28541819849	2026-07-01 19:17	✅ success	30.11	6
§28541604605	2026-07-01 19:13	✅ success	52.21	4
§28540470721	2026-07-01 18:53	❌ failure	—	2
§28540402795	2026-07-01 18:52	✅ success	52.26	5
§28523149542	2026-07-01 14:00	✅ success	52.26	5
§28520768575	2026-07-01 13:22	✅ success	53.52	4

Workflows Without Token Data

All 18 runs had token_usage = null and estimated_cost = null. The Smoke Claude workflow does not appear to have the AWF api-proxy sidecar instrumented for token tracking.

To enable token telemetry, add --enable-api-proxy to the AWF invocation in .github/workflows/smoke-claude.lock.yml. This will surface:

• Per-turn input/output token counts
• Prompt cache hit/write rates (Anthropic)
• USD cost estimates per run
• Model breakdown if multiple models are used

Historical Trend

This is the first Claude token usage report — no prior reports exist for comparison.

References:

• §28579027272 (this workflow run)

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• awmgmcpg

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by Daily Claude Token Usage Analyzer · 32.9 AIC · ⊞ 7.7K · ◷

[github-actions]

This issue is being closed as outdated. A newer issue has been created: #5863

View newer issue

---

This action was performed automatically by the Daily Claude Token Usage Analyzer workflow.