📊 Daily Copilot Token Consumption Report - December 23, 2025 #7383
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it was created by an agentic workflow more than 3 days ago. |
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 4 days (December 20-23, 2025), Copilot-powered agentic workflows consumed 159.6 million tokens at an estimated cost of $4.79, across 402 workflow runs covering 46 unique workflows.
Key Highlights:
Full Report Details
📈 Token Usage Trends
Daily Breakdown (Last 4 Days)
Trend Analysis: Token consumption spiked significantly on December 21-22 (weekdays) with 139-204 runs per day, representing the typical workday load. December 23 shows reduced activity as we approach the holidays. Weekend baseline (Dec 20) shows minimal activity with only 2 runs.
Activity Patterns
🏆 Top 15 Workflows by Token Consumption
Top 5 Analysis
1. Hourly CI Cleaner (29.4% of total cost)
2. Issue Monster (8.5% of total cost)
3. Tidy (8.1% of total cost)
4. Spec-Kit Execute (6.4% of total cost)
5. Smoke Copilot No Firewall (4.7% of total cost)
📊 Cost Distribution
Top 5 workflows account for 57.0% of total costs:
Remaining 41 workflows: $2.06 (43.0%)
💡 Insights & Recommendations
High-Cost Workflow Analysis
1. Hourly CI Cleaner - $1.41 (29% of total)
Observation: This scheduled workflow consumes nearly 1M tokens per run, executing 48 times over 4 days (hourly). Its per-run consumption is 2.5x the repository average.
Recommendations:
$0.70/4 days ($5/month)2. Issue Monster + Tidy - $0.80 combined (16.6% of total)
Observation: Both are high-frequency scheduled workflows with moderate per-run consumption (300K-314K tokens). Combined they run 86 times over 4 days.
Recommendations:
3. High Per-Run Consumers (>1M tokens/run)
Several workflows consume over 1M tokens per run:
Recommendations:
Efficiency Opportunities
1. AI Moderator - High Efficiency Example
Stats: 99 runs, only 32K tokens/run, $0.0010/run
Pattern to replicate:
2. Scheduled vs. Event-Driven Workflows
Observation: Scheduled workflows (Hourly CI Cleaner, Issue Monster, Tidy) dominate costs because they run regardless of whether work exists.
Recommendation:
Cost Trend Analysis
4-Day Period Breakdown:
Projection: Typical workweek consumption appears to be ~$1.50-$2.50/day, with weekends at ~$0.02/day.
Monthly estimate: ~$35-50/month during active development periods
🎯 Priority Optimization Recommendations
Immediate Actions (High Impact, Low Effort)
Reduce Hourly CI Cleaner frequency
Add no-op detection to scheduled workflows
Review high per-run consumers for context optimization
Medium-Term Actions (High Impact, Medium Effort)
Consolidate similar maintenance workflows
Implement smart triggering for scheduled workflows
Long-Term Monitoring
Establish token budgets per workflow
Regular efficiency reviews
📅 Historical Comparison
Key Insights:
🔧 Methodology
/tmp/gh-aw/cache-memory/token-metrics/history.jsonl📊 Data Quality Notes
📦 Repository Statistics
Next Steps:
References:
Beta Was this translation helpful? Give feedback.
All reactions