[api-consumption] 📊 GitHub API Consumption Report — 2026-08-29

[github-actions[bot]]

📊 GitHub API Consumption Report

Report Date: 2026-08-29 · Repository: github/gh-aw · Run: #33248482131

---

Today at a Glance

Metric	Value
🤖 Total Runs	185 (162 ✅ / 23 ❌)
🎯 Success Rate	87.57%
🔗 GitHub REST API Calls	68,868 (core quota consumed — includes reads, writes, and all GitHub API operations)
📝 Safe-Output Writes	353 (issues + PRs + comments + discussions created by safe-output tools)
⏱ Avg Duration	548.7s (p95: 1332.6s)

Note: log collection this run was partial — see the Cache Memory Status block below — so today's totals reflect the fetched window (2026-08-28T18:08Z–2026-08-29T10:39Z, ~16.5h) rather than a full clean UTC day.

---

🔗 GitHub API Calls Trend (90 days)

History is still thin (11 tracked days, with gaps on several dates due to prior partial collections) so this reads as a sawtooth rather than a smooth trend. The largest spike was 2026-08-15 (~398K calls, driven by a burst of high-volume runs), with a second peak on 2026-08-23 (~290K). The 7-day rolling average has drifted down from ~200K to ~107K over the tracked window, and today's 68,868 calls sit below that average.

---

🔗 GitHub API Calls by Workflow Trend (30 days)

PR Sous Chef is the most volatile top consumer, spiking to ~69K calls on its first tracked day before settling to single-digit thousands most other days. The four skills-reviewer workflows (Matt Pocock Skills Reviewer, Impeccable Skills Reviewer, Ponytail Reviewer, Design Decision Gate) move almost in lockstep around 20–28K calls per day whenever they run, then drop off sharply — consistent with batch PR-review triggers rather than steady background load.

---

🔗 GitHub REST API Calls Heatmap (90 days)

Fewer than 14 history data points exist, so this panel falls back to today's top-10-workflow bar chart per the documented fallback rule. PR Sous Chef dominates today's consumption at 11,895 calls (17.3% of the 24h total), roughly 2.7× the next-highest consumer (Issue Monster, 4,346 calls). A cluster of workflows — Code Simplifier, Daily AstroStyleLite Markdown Spellcheck, Go Logger Enhancement — each land close to 4,000 calls despite being single-run, one-off workflows today.

---

🍩 Top API Burners (24h)

The top 10 workflows account for 56.3% of today's 68,868 REST API calls, with the remaining 43.7% (~30,061 calls) spread across 100+ other workflows that ran in the window — a moderately concentrated but not dangerously top-heavy distribution. PR Sous Chef alone is responsible for more than double the combined share of the next three workflows, making it the single workflow most worth watching if quota pressure increases.

---

🔗 GitHub REST API Consumption by Workflow (last 24h)

No workflow is anywhere near the 15,000/hour core quota limit — PR Sous Chef's 11,895 calls is its highest observed run-level consumption today, but that figure is aggregated across 37 runs, not a single hour. Still, PR Sous Chef and Issue Monster (37 and 20 runs respectively) are the two workflows with materially higher run counts than the rest, so they're the natural first candidates if per-run API usage needs to be trimmed (e.g. batching GraphQL queries, caching repeated lookups).

---

Top 10 Workflows by REST API Consumption (last 24h)

Workflow	REST API Calls	Runs	Avg Duration
PR Sous Chef	11,895	37	490.6s
Issue Monster	4,346	20	393.6s
Code Simplifier	3,994	1	801.0s
Daily AstroStyleLite Markdown Spellcheck	3,992	1	501.0s
Go Logger Enhancement	3,981	1	777.0s
Smoke Project	3,064	1	432.0s
Code Scanning Fixer	2,081	2	1490.0s
Smoke Checkout PR Dispatch	1,842	1	313.0s
Chaos PR Bundle Fuzzer	1,833	1	463.0s
Smoke Copilot	1,779	1	634.0s

---

Trending Indicators

• 7-day API trend: → insufficient data (history has 11 tracked days with gaps; need 14 consecutive days of data for a reliable 7-day-over-7-day comparison)
• 30-day API trend: → insufficient data (need 60 tracked days; history spans 2026-08-14 to 2026-08-29 with several gaps)
• GitHub REST API call rate: ~105,890 calls/day average over the last 7 tracked entries (hourly limit: 15,000) — note this average is skewed by partial-window collection days and should be treated as directional, not exact

---

📦 Cache Memory Status

• Location: /tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonl
• Cache restored from previous run: yes (10 existing entries)
• Collection mode: backfill
• Logs start_date used: -90d (requested), but MCP count-limit pagination stopped after 2 continuation calls, actually covering only 2026-08-28T18:08:13Z through 2026-08-29T10:39:32Z (~16.5 hours) of the requested 90-day window
• Data points stored: 11
• Earliest entry: 2026-08-14
• Retention policy: 90 days

Known limitation: Both today's entry and the backfilled 2026-08-28 entry are based on partial log coverage, not full calendar days — several prior history entries carry the same limitation (see their own partial_data_note fields). Trend indicators above are marked "insufficient data" rather than computed from a skewed partial sample.

---

Automatically generated by the api-consumption-report workflow.

Warning

Firewall blocked 1 domain

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

• api.anthropic.com

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

network:
  allowed:
    - defaults
    - "api.anthropic.com"

See Network Configuration for more information.

Generated by 📊 GitHub API Consumption Report Agent · claude · agent · 179.8 AIC · ⌖ 8.04 AIC · ⊞ 13.4K · ◷

• expires on Sep 1, 2026, 3:00 AM UTC-08:00

[github-actions[bot]]

This discussion was automatically closed because it expired on 2026-09-01T11:00:05.470Z.

Closed by Workflow