You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
79,196 (core quota consumed β includes reads, writes, and all GitHub API operations)
π Safe-Output Writes
254 (issues + PRs + comments + discussions created by safe-output tools)
β± Avg Duration
585.2s (p95: 1146.0s)
π GitHub API Calls Trend (90 days)
Total REST API consumption is trending up modestly, at 79.2K today versus a 7-day rolling average in the 70β100K band. The dominant feature of the window remains the 2026-06-15 spike (~575K) β roughly 7Γ a normal day β which still pulls the rolling average upward weeks later. Outside that anomaly, daily volume oscillates between ~15K and ~185K with no runaway growth.
π GitHub API Calls by Workflow Trend (30 days)
The heaviest consumers over the last 30 days are consistently the PR- and skills-review workflows β PR Code Quality Reviewer, Test Quality Sentinel, Impeccable/Matt Pocock Skills Reviewer, and Design Decision Gate. These review agents run per-PR and per-skill, so their aggregate quota scales directly with repository activity rather than any single expensive run.
π GitHub REST API Calls Heatmap (90 days)
The heatmap shows consumption concentrated on weekdays, tracking PR and CI activity, with lighter weekend cells. The single darkest cell corresponds to the mid-June anomaly; no other day approaches it, indicating that spike was an isolated event rather than a recurring weekly pattern.
Consumption is moderately concentrated: the top 5 workflows account for ~61% of all REST API quota used today, and the single largest β PR Code Quality Reviewer (15.1%) β is a review agent, not a batch job. With 97 distinct workflows sharing the remaining ~39%, there is no single point of runaway consumption, but the review cluster is worth watching if PR volume grows.
π GitHub REST API Consumption by Workflow (last 24h)
The top consumer, PR Code Quality Reviewer, used 11,930 calls across 9 runs (~1.3K/run) β comfortably below the 15,000/hr limit with ~3,070 headroom, and spread across the day rather than concentrated in a single hour. No workflow breached or approached the hourly ceiling. The clearest optimisation target is the review-agent cluster: caching repeated contents/pulls reads or batching review-comment writes would trim the largest recurring line items.
Top 10 Workflows by REST API Consumption (last 24h)
Workflow
REST API Calls
Runs
Avg Duration
PR Code Quality Reviewer
11,930
9
557s
Impeccable Skills Reviewer
9,988
8
465s
Test Quality Sentinel
9,282
9
473s
Design Decision Gate ποΈ
8,967
9
438s
Matt Pocock Skills Reviewer
8,085
9
534s
PR Description Updater
7,042
7
461s
Smoke CI
5,473
8
253s
PR Sous Chef
3,085
10
405s
Smoke Copilot - AOAI (Entra)
2,023
4
835s
Smoke Antigravity
1,485
4
345s
Trending Indicators
7-day API trend: β +6.2% vs. previous 7 days
30-day API trend: β (insufficient data β 54 of 60 required days collected)
GitHub REST API call rate: ~72,796 calls/day over last 7 days (hourly limit: 15,000)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
π GitHub API Consumption Report
Report Date: 2026-07-13 Β· Repository: github/gh-aw Β· Run: #29247097459
Today at a Glance
π GitHub API Calls Trend (90 days)
Total REST API consumption is trending up modestly, at 79.2K today versus a 7-day rolling average in the 70β100K band. The dominant feature of the window remains the 2026-06-15 spike (~575K) β roughly 7Γ a normal day β which still pulls the rolling average upward weeks later. Outside that anomaly, daily volume oscillates between ~15K and ~185K with no runaway growth.
π GitHub API Calls by Workflow Trend (30 days)
The heaviest consumers over the last 30 days are consistently the PR- and skills-review workflows β PR Code Quality Reviewer, Test Quality Sentinel, Impeccable/Matt Pocock Skills Reviewer, and Design Decision Gate. These review agents run per-PR and per-skill, so their aggregate quota scales directly with repository activity rather than any single expensive run.
π GitHub REST API Calls Heatmap (90 days)
The heatmap shows consumption concentrated on weekdays, tracking PR and CI activity, with lighter weekend cells. The single darkest cell corresponds to the mid-June anomaly; no other day approaches it, indicating that spike was an isolated event rather than a recurring weekly pattern.
π© Top API Burners (24h)
Consumption is moderately concentrated: the top 5 workflows account for ~61% of all REST API quota used today, and the single largest β PR Code Quality Reviewer (15.1%) β is a review agent, not a batch job. With 97 distinct workflows sharing the remaining ~39%, there is no single point of runaway consumption, but the review cluster is worth watching if PR volume grows.
π GitHub REST API Consumption by Workflow (last 24h)
The top consumer, PR Code Quality Reviewer, used 11,930 calls across 9 runs (~1.3K/run) β comfortably below the 15,000/hr limit with ~3,070 headroom, and spread across the day rather than concentrated in a single hour. No workflow breached or approached the hourly ceiling. The clearest optimisation target is the review-agent cluster: caching repeated
contents/pullsreads or batching review-comment writes would trim the largest recurring line items.Top 10 Workflows by REST API Consumption (last 24h)
Trending Indicators
π¦ Cache Memory Status
/tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonlAutomatically generated by the api-consumption-report workflow.
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
awmgmcpgSee Network Configuration for more information.
Beta Was this translation helpful? Give feedback.
All reactions