[portfolio] Portfolio Analysis Dashboard - Dec 13, 2025

[github-actions[bot]]

📊 Portfolio Dashboard - December 13, 2025

Quick Overview

Analysis of 536 workflow runs across 75 workflows over a 2-day period (Dec 11-13, 2025) reveals $24/period in savings opportunities through failure remediation and frequency optimization. Current spending: $67 with a 69% success rate and concerning failure patterns in scheduled workflows.

⚠️ Data Confidence: MEDIUM - Analysis based on 2-6 days of execution history. Patterns may not be fully representative. Recommend re-running after 7+ days for higher confidence.

Visual Summary

Daily Spending Pattern

Dec 11: $22.26 average daily cost
Dec 12: $22.26 average daily cost  
Dec 13: $22.26 average daily cost
Trend: STABLE (3-day period)

Cost Distribution

• Top 3 workflows account for 30% of total cost ($20.23)
• 56 workflows executed successfully at least once
• 10 workflows with 100% failure rate (disabled candidates)

Overall Health Metrics

✅ Success:    372 runs (69%)
❌ Failure:     67 runs (13%)
⏸️ Cancelled:   97 runs (18%)

Top Cost Drivers

Rank	Workflow	Cost	Runs	Success Rate	Status
1	Hourly CI Cleaner	$8.86	56	48%	⚠️ High failure
2	Tidy	$5.86	56	59%	⚠️ Low success
3	Issue Monster	$5.51	41	98%	✅ Healthy
4	Spec-Kit Execute	$2.92	9	100%	✅ Healthy
5	Go Logger Enhancement	$2.83	2	100%	✅ Healthy
6	Smoke Claude	$2.49	23	91%	✅ Healthy
7	Static Analysis Report	$2.26	3	100%	✅ Healthy
8	Instructions Janitor	$1.99	3	100%	✅ Healthy
9	CLI Version Checker	$1.77	4	100%	✅ Healthy
10	Agentic Workflow Audit Agent	$1.72	2	100%	✅ Healthy

Failure Analysis - Top Wasters

Workflow	Failure Rate	Failed Runs	Wasted Cost
Hourly CI Cleaner	52%	29/56	$4.59
The Daily Repository Chronicle	50%	1/2	$0.70
CI Optimization Coach	62%	5/8	$0.46
Semantic Function Refactoring	33%	1/3	$0.34

Total Wasted on Failures: $6.09

💰 Cost Reduction Opportunities

Total Potential Savings: $23.97/period (36% reduction)

Strategy 1: Fix High-Failure Workflows - $4.59/period

Hourly CI Cleaner - 52% Failure Rate

**(redacted) .github/workflows/hourly-ci-cleaner.md

Problem: 29 out of 56 runs failed, wasting $4.59

Impact: Single biggest waste contributor

Recommended Actions:

1. Review error logs to identify common failure patterns
2. Add error handling for known failure cases
3. Consider changing from hourly to daily schedule (see Strategy 2)
4. Add pre-flight checks to fail fast on known issues

Estimated Savings: $4.59/period by fixing failures, plus additional savings from frequency reduction

---

Other High-Failure Workflows

The Daily Repository Chronicle - 50% failure (1/2 runs)

• Cost wasted: $0.70
• Action: Review the 1 failed run and fix root cause

CI Optimization Coach - 62% failure (5/8 runs)

• Cost wasted: $0.46
• Action: Debug why 5 of 8 runs fail

Strategy 2: Reduce Over-Scheduling - $18.68/period

Multiple workflows run far more frequently than needed. Reducing to 4 runs/day would maintain coverage while cutting costs.

Hourly CI Cleaner

Current: 28 runs/day (hourly)
Recommended: 4 runs/day (every 6 hours)
Savings: $7.60/period

Rationale: CI cleaning doesn't need hourly execution. Every 6 hours provides adequate coverage.

Implementation:

# File: .github/workflows/hourly-ci-cleaner.md
# Change trigger from:
on:
  schedule:
    - cron: '0 * * * *'  # Every hour

# To:
on:
  schedule:
    - cron: '0 */6 * * *'  # Every 6 hours

---

Tidy

Current: 28 runs/day (hourly)
Recommended: 4 runs/day (every 6 hours)
Savings: $5.02/period

Implementation:

# File: .github/workflows/tidy.md
# Change trigger from hourly to every 6 hours
on:
  schedule:
    - cron: '0 */6 * * *'

---

Issue Monster

Current: 20 runs/day
Recommended: 4 runs/day (every 6 hours)
Savings: $4.43/period

Implementation:

# File: .github/workflows/issue-monster.md
# Reduce frequency to every 6 hours

---

Smoke Claude

Current: 12 runs/day
Recommended: 4 runs/day
Savings: $1.63/period

Strategy 3: Disable 100% Failed Workflows - $0.00 immediate

The following workflows have never succeeded and should be disabled until fixed:

1. Daily Project Performance Summary Generator (Using Safe Inputs) - 3/3 failures
2. Copilot Session Insights - 2/2 failures
3. Super Linter Report - 2/2 failures
4. Issue Triage Agent - 2/2 failures
5. Daily Copilot Token Consumption Report - 2/2 failures

Action: Add if: false to workflow triggers until issues are resolved:

# Add to each workflow
on:
  schedule:
    - cron: '...'
  workflow_dispatch:
    
# Add this line to disable:
if: false  # Disabled until [issue #XXX] is resolved

Note: These workflows currently cost $0.00 (failed before token usage), but waste execution time and clutter logs.

Strategy 4: Monitor Recently Healthy Workflows

These workflows are currently performing well but should be monitored:

Excellent Performers (100% success):

• Spec-Kit Execute - $2.92 (9 runs)
• Go Logger Enhancement - $2.83 (2 runs)
• Static Analysis Report - $2.26 (3 runs)
• Instructions Janitor - $1.99 (3 runs)
• CLI Version Checker - $1.77 (4 runs)

Good Performers (>90% success):

• Issue Monster - $5.51 (98% success, 41 runs)
• Smoke Claude - $2.49 (91% success, 23 runs)

Action: No changes needed. Continue monitoring.

🎯 Priority Actions

1. CRITICAL - Fix Hourly CI Cleaner failure rate (52% → <10%) - $4.59 savings + improved reliability

   • File: .github/workflows/hourly-ci-cleaner.md
   • Review error logs, add error handling, implement pre-flight checks

2. HIGH - Reduce Hourly CI Cleaner frequency (hourly → every 6 hours) - $7.60 savings

   • File: .github/workflows/hourly-ci-cleaner.md
   • Change cron: '0 */6 * * *'

3. HIGH - Reduce Tidy frequency (hourly → every 6 hours) - $5.02 savings

   • File: .github/workflows/tidy.md
   • Change cron: '0 */6 * * *'

4. MEDIUM - Reduce Issue Monster frequency (20/day → 4/day) - $4.43 savings

   • File: .github/workflows/issue-monster.md
   • Change to every 6 hours schedule

5. LOW - Disable 10 workflows with 100% failure rate - Improved clarity

   • Add if: false to prevent wasted execution time

📈 Data Quality & Methodology

Analysis Period

• Dates Covered: December 11-13, 2025 (2 days)
• Total Runs: 536 workflow executions
• Workflows: 75 total, 56 executed successfully at least once
• Confidence: MEDIUM - 2-6 days of history available

Data Limitations

⚠️ Important Caveats:

• Only 2 days of execution data available
• Patterns may not represent typical weekly/monthly behavior
• Weekend vs. weekday patterns not captured
• Some workflows may not have run during this period
• Cost projections are based on 2-day sample, not full month

Confidence Recommendations

• Current analysis: Good for identifying obvious issues (high failure rates, over-scheduling)
• For strategic decisions: Re-run analysis after 7+ days for higher confidence
• For monthly budgeting: Need 30-day history for accurate projections

Calculation Methodology

• Costs: Calculated from actual token usage at $0.00035 per 1K tokens
• Failure rates: Based on workflow conclusion status (success/failure/cancelled)
• Wasted spend: Cost of failed runs (actual tokens consumed before failure)
• Savings projections: Based on 2-day average; scale accordingly for monthly estimates

Next Steps

1. Implement high-priority fixes (Hourly CI Cleaner frequency + failures)
2. Monitor impact over 7 days
3. Re-run portfolio analysis after 7-14 days for validation
4. Adjust other workflows based on validated patterns

---

Methodology: Analysis based on actual workflow execution data from gh aw logs for December 11-13, 2025. Costs calculated from real token usage via Copilot API, not estimates. See /tmp/portfolio-logs/summary.json for raw data.

AI generated by Automated Portfolio Analyst

[github-actions[bot]]

⚓ Avast! This discussion be marked as outdated by Automated Portfolio Analyst.
🗺️ A newer treasure map awaits ye at Discussion #6499.
Fair winds, matey! 🏴‍☠️