📊 Daily Copilot Token Consumption Report - 2026-02-10 #14768
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it expired on 2026-02-13T11:43:23.559Z.
|
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, Copilot-powered agentic workflows consumed 220,651,611 tokens at an estimated cost of $220.65, across 437 workflow runs covering 59 unique workflows.
Key Highlights:
📈 Token Usage Trends
Overall Trends
The chart above shows daily token consumption. This is the first data point in our historical tracking - future reports will show trends over time as we collect more data.
Cost Trends
Daily cost trends are now being tracked. As we collect more data points, we'll be able to identify patterns, efficiency improvements, and optimization opportunities.
🏆 Top Workflows by Token Consumption
Top 10 Most Expensive Workflows
Per-Workflow Detailed Statistics (All Workflows)
💡 Insights & Recommendations
High-Cost Workflows
The following workflows account for the majority of token consumption:
CI Failure Doctor - $60.34 (27.3% of total)
Chroma Issue Indexer - $35.00 (15.9% of total)
Security Guard Agent 🛡️ - $13.51 (6.1% of total)
Top 3 workflows account for 49.3% of total token consumption.
Optimization Opportunities
Based on the initial analysis, here are potential optimization opportunities:
High Per-Run Token Usage: Workflows with >1M tokens per run
High-Volume Workflows: Workflows with >20 runs
Historical Tracking: Future opportunities
Efficiency Metrics
Token Efficiency Analysis
Overall average: 0.5049 per run (504924 tokens/run)
Most efficient workflows (lowest tokens per run):
Least efficient workflows (highest tokens per run):
Cost Efficiency Insights
Historical Comparison
Note: This is the first daily report. Historical comparisons will be available starting tomorrow when we have multiple data points to compare.
Future reports will include:
Current Baseline (for future reference):
Methodology & Data Quality Notes
Methodology
/tmp/gh-aw/repo-memory/default/history.jsonlData Quality Notes
Future Enhancements
References:
Beta Was this translation helpful? Give feedback.
All reactions