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

[github-actions[bot]]

Warning

Threat Detection Engine Failure — The analysis engine could not complete. This is a tooling failure, not a security finding.

What happened

The threat detection engine failed to produce results.

Review the workflow run logs for details.

📊 GitHub API Consumption Report

Report Date: 2026-08-06 · Repository: github/gh-aw · Run: #31097485447

---

Today at a Glance

Metric	Value
🤖 Total Runs	203 (188 ✅ / 15 ❌)
🎯 Success Rate	92.61%
🔗 GitHub REST API Calls	246,799 (core quota consumed — includes reads, writes, and all GitHub API operations)
📝 Safe-Output Writes	315 (issues + PRs + comments + discussions created by safe-output tools)
⏱ Avg Duration	553.64s (p95: 1080.9s)

---

🔗 GitHub API Calls Trend (90 days)

Only 2 calendar days of run history are currently available (2026-08-05 and 2026-08-06) — this is the first run of the trending pipeline, so cache-memory history is just being seeded. Day-over-day, total REST API consumption jumped from 61,589 calls (2026-08-05) to 246,799 calls (2026-08-06), a ~4x increase driven by a much larger batch of PR-review and skills-reviewer workflows running on 08-06. No multi-week trend can be established yet; this chart will fill in as daily runs accumulate.

---

🔗 GitHub API Calls by Workflow Trend (30 days)

With only 2 days of history, "Test Quality Sentinel," "PR Code Quality Reviewer," "Matt Pocock Skills Reviewer," "Impeccable Skills Reviewer," and "Design Decision Gate 🏗️" are the top 5 workflows by total API calls — all five appeared with negligible or zero consumption on 08-05 and became the dominant consumers on 08-06, suggesting these PR-review workflows fire in bursts tied to PR activity volume rather than a steady daily cadence.

---

🔗 GitHub REST API Calls Heatmap (90 days)

Fewer than 14 days of history exist, so this panel falls back to a bar chart of today's top workflows by REST API consumption rather than a calendar heatmap. "Test Quality Sentinel," "PR Code Quality Reviewer," and "Matt Pocock Skills Reviewer" lead today's consumption, each in the 20K-call range — a genuine weekly/monthly heatmap will render automatically once 14+ days of history accumulate in cache-memory.

---

🍩 Top API Burners (24h)

The top 10 workflows account for the large majority of today's 246,799 REST API calls, with "Test Quality Sentinel" (21,265), "PR Code Quality Reviewer" (20,965), and "Matt Pocock Skills Reviewer" (20,008) each individually consuming roughly 8-9% of the daily total. Concentration risk is moderate — no single workflow dominates, but the top 5 PR-review-oriented workflows together account for over 40% of today's quota.

---

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

"Test Quality Sentinel" (21,265), "PR Code Quality Reviewer" (20,965), and "Matt Pocock Skills Reviewer" (20,008) are today's top REST API consumers, all well under the 15,000/hour rate limit on a per-run basis (each spread across many runs), but their combined daily total is worth monitoring if PR volume keeps growing. No workflow is individually near the hourly limit; the main optimisation opportunity is reducing per-run API calls in the four skills/quality-reviewer workflows, which together account for ~81K calls today.

---

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

Workflow	REST API Calls	Runs	Avg Duration
Test Quality Sentinel	21,265	16	499.3s
PR Code Quality Reviewer	20,965	14	650.5s
Matt Pocock Skills Reviewer	20,008	14	473.4s
Impeccable Skills Reviewer	18,922	14	414.2s
Design Decision Gate 🏗️	17,111	14	360.6s
PR Sous Chef	13,206	12	434.3s
Issue Monster	12,468	10	355.6s
AI Moderator	11,042	4	381.8s
PR Description Updater	7,000	5	370.6s
Auto-Triage Issues	5,523	8	395.5s

---

Trending Indicators

• 7-day API trend: → insufficient data (only 2 days of history collected so far; need 14 days for a 7-day-vs-prior-7-day comparison)
• 30-day API trend: → insufficient data (only 2 days of history collected so far; need 60 days for a 30-day-vs-prior-30-day comparison)
• GitHub REST API call rate: ~154,194 calls/day averaged over the 2 available days (hourly limit: 15,000) — not yet a stable 7-day figure

---

📦 Cache Memory Status

• Location: /tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonl
• Cache restored from previous run: no (first run)
• Collection mode: backfill
• Logs start_date used: -90d (only 2 days of actual run history exist in this environment; 3 log-fetch calls were made — 1 initial + 2 continuations — and the dataset is confirmed complete since the final continuation returned no further pagination token)
• Data points stored: 2
• Earliest entry: 2026-08-05
• Retention policy: 90 days

---

Automatically generated by the api-consumption-report workflow.

Generated by 📊 GitHub API Consumption Report Agent · agent · 188.6 AIC · ⊞ 12.5K · ◷

• expires on Aug 9, 2026, 3:50 AM UTC-08:00

[github-actions[bot]]

This discussion has been marked as outdated by GitHub API Consumption Report Agent.

A newer discussion is available at Discussion #51054.