📊 Claude Token Usage Report2026-05-26
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- github-actions
- Domain
- observability
Research direction
Review the linked Security Guard and Smoke Claude GitHub Actions runs, then compare them with the previous report in issue 3741. Trace the recent change associated with the token and error-rate increases; done means the cause is identified and the affected workflows no longer exhibit the reported waste or failures.
Written by the indexing model from the issue text.
Description
Overview
Period: 2026-05-25 to 2026-05-26
Runs analyzed: 50 (50 had token data)
Total tokens: 16,603K across all workflows
Estimated total cost: $9.58
Total Actions minutes: 194 min
All runs use claude-haiku-4-5-20251001 (Haiku 4.5) via the AWF api-proxy sidecar.
⚠️ Significant cost increase vs yesterday: $9.58 today vs $3.97 yesterday (+141%). Security Guard run count increased from 19 → 23 runs and avg tokens/run increased from 72K → 363K (5× increase).
Workflow Summary
| Workflow | Runs | Total Tokens | Avg Tokens | Cost | Avg Cost | Turns | Errors |
|---|---|---|---|---|---|---|---|
| Security Guard | 23 | 8,352K | 363K | $6.89 | $0.30 | 138 | 10/23 |
| Smoke Claude | 26 | 8,145K | 313K | $2.61 | $0.10 | 132 | 2/26 |
| Documentation Maintainer | 1 | 106K | 106K | $0.08 | $0.08 | 2 | 0/1 |
🔍 Optimization Opportunities
-
Security Guard — $0.30/run avg, 43% failure rate (10/23 runs failed)
- High error rate (43% > 30% threshold): Failing runs still consume ~363K tokens/run on average, burning ~$3–4 in failed runs alone
- High token count (363K avg >> 100K threshold): 5× higher than yesterday's 72K avg — investigate what changed in the system prompt or tool surface
- Consider adding early exit conditions to reduce token waste on failing runs
-
Smoke Claude — 313K avg tokens/run (>> 100K threshold)
- Token count is high for a smoke test workflow; review whether all MCP tools and context are necessary for basic smoke validation
- Cache ratio is healthy (read: 6.8M vs write: 1.3M) — caching is working well
-
Documentation Maintainer — cache_write ≈ cache_read (53K vs 52K)
- Only 1 run; on first run there's no prior cache to reuse — this is expected behavior
Per-Workflow Details
Security Guard
- Runs: 23 — 26415810244 26416831183 26417325822 26418046174 26418335198 26419350967 26419769120 26420916882 26421535927 26422813917 26423269838 26423290817 26424429129 26424917289 26424932691 26424942594 26424949514 26425052417 26425126879 26425202438 26426825329 26426891074 26428636563
- Success rate: 14/23 (61%)
- Total tokens: 8,352K (avg 363K/run)
- Estimated cost: $6.89 (avg $0.30/run)
- Turns: 138 total (avg 6.0/run)
- Cache analysis: write 1,073K / read 7,250K — cache reuse ratio is good (6.8× more reads than writes)
- Error rate: 10/23 runs with errors
Smoke Claude
- Runs: 26 — 26415729622 26415810298 26416831121 26417325819 26418046141 26418335203 26419090188 26419350968 26419769056 26420916881 26421535897 26422813947 26423269773 26423290861 26424429137 26424917327 26424932707 26424942523 26424949584 26425052440 26425126880 26425202434 26426825373 26426883407 26426891075 26428636529
- Success rate: 25/26 (96%)
- Total tokens: 8,145K (avg 313K/run)
- Estimated cost: $2.61 (avg $0.10/run)
- Turns: 132 total (avg 5.1/run)
- Cache analysis: write 1,322K / read 6,793K — healthy cache reuse (5.1× more reads than writes)
- Error rate: 2/26 runs with errors
Documentation Maintainer
- Runs: 1 — 26435014666
- Success rate: 1/1 (100%)
- Total tokens: 106K (avg 106K/run)
- Estimated cost: $0.08 (avg $0.08/run)
- Turns: 2 total (avg 2.0/run)
- Cache analysis: write 53K / read 52K — first run, no prior cache to reuse (expected)
- Error rate: 0/1 runs
Workflows Without Token Data
All 50 runs had token data. No workflows are missing instrumentation.
Historical Trend
| Metric | 2026-05-24→25 | 2026-05-25→26 | Change |
|---|---|---|---|
| Total runs | 42 | 50 | +19% |
| Total tokens | 5,573K | 16,603K | +198% ⚠️ |
| Total cost | $3.97 | $9.58 | +141% ⚠️ |
| Security Guard avg tokens | 72K | 363K | +404% ⚠️ |
| Security Guard cost | $2.50 | $6.89 | +176% |
| Security Guard error rate | 53% (10/19) | 43% (10/23) | -10pp ✅ |
| Smoke Claude avg tokens | 188K | 313K | +67% |
| Smoke Claude cost | $1.42 | $2.61 | +84% |
The Security Guard workflow is the primary cost driver. While its error rate improved slightly (53% → 43%), average tokens per run jumped 5× — suggesting a significant prompt or context expansion in recent changes.
Previous Report
References:
- §26444011247 — this workflow run
Generated by Daily Claude Token Usage Analyzer · sonnet46 1.2M · ◷
- Dominant language
- TypeScript
- Stars
- 149
- Forks
- 77
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 418
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/gh-aw-firewall
-
agentic-workflows automated dependencies
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/gh-aw-firewall#3837 ·
Maintainers usually reply within 1 day
-
agentic-workflows
Difficulty 4/5 3-5 days Newbie friendliness 25/100
github/gh-aw-firewall#10175 ·
Maintainers usually reply within 1 day
-
agentic-workflows
Difficulty 4/5 3-5 days Newbie friendliness 35/100
github/gh-aw-firewall#10174 ·
Maintainers usually reply within 1 day
-
agentic-workflows
Difficulty 4/5 3-5 days Newbie friendliness 25/100
github/gh-aw-firewall#10173 ·
Maintainers usually reply within 1 day
-
feat: native protected command-output capture outside agent-visible mountsPossibly taken @lpcox claimed this today. Open
github/gh-aw-firewall#10166 · 1 reaction · 2 assignees ·
Maintainers usually reply within 1 day
All issues in github/gh-aw-firewall
Similar issues
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 90/100
lingdojo/kana-dojo#32663 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Admin: Title Separator field can't be cleared (input falls back to "|")Possibly taken @emdashbot claimed this today. Openbot:bug bot:in-review
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
emdash-cms/emdash#4236 · 3 comments ·
Maintainers usually reply within 1 day
-
PHP workflow streaming requests buffer the full SSE responsePossibly taken @Winoren claimed this today. Openreview: medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
langgenius/dify#44270 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
area:holodeck review-finding
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
hyperdrive-technology/holodeck#142 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
code-yeongyu/senpi#3573 ·
Maintainers usually reply within 1 day