π Daily Copilot Token Consumption Report β 2026-03-20 #21952
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by Daily Copilot Token Consumption Report. A newer discussion is available at Discussion #22415. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Executive Summary
Over the last 30 days (as of 2026-03-20), Copilot-powered agentic workflows consumed 58,187,531 tokens across 96 workflow runs covering 47 unique workflows. The average token usage per run was 606,120 tokens. Cost data is not available in the current log format.
Key Highlights
π Visual Analytics
Top 15 Workflows by Total Token Consumption
Top 15 Most Active Workflows (by Run Count)
Top 15 Workflows by Average Tokens per Run
π Top 15 Workflows by Token Consumption
Per-Workflow Detailed Statistics (All 47 Workflows)
π‘ Insights & Recommendations
High Single-Run Cost Workflows
Several workflows consumed over 2M tokens in a single run β these are prime candidates for optimization review:
Daily Syntax Error Quality Check β 4.16M tokens/run
GitHub Remote MCP Authentication Test β 3.46M tokens/run
Ubuntu Actions Image Analyzer β 3.15M tokens/run
Optimization Opportunities
Incremental scanning for quality check workflows (Syntax Error, Compiler Quality, Malicious Code Scan)
git diff --name-only HEAD~1scoping to limit analysis to recently modified filesOutput verbosity controls for research agents
max_output_tokensguidance or structured output formats to workflow promptsIssue Monster token efficiency β already excellent
Contribution Check batching
Workflow Health Summary
Runs missing token data (by workflow):
Historical Tracking Note
This is the first run of the token consumption report with historical tracking enabled. Today's aggregated metrics have been stored in repo memory at
memory/token-metrics/history.jsonl(branch:memory/token-metrics).Future reports will include:
Cost Data: The current log format reports
total_cost: 0in the summary. Once cost data becomes available in the logs, it will be incorporated into future reports automatically.References: Β§23340261754
Beta Was this translation helpful? Give feedback.
All reactions