budget

24h timestamp (GNU): !date --version 2>/dev/null | grep -q GNU && date -d '24 hours ago' -Iseconds || echo "N/A"

24h timestamp (BSD): !date --version 2>/dev/null | grep -q GNU || date -u -v-24H -Iseconds 2>/dev/null || echo "N/A"

Marketing deployments (24h): !SINCE=$(date --version 2>/dev/null | grep -q GNU && date -d '24 hours ago' -Iseconds || date -u -v-24H -Iseconds); gh run list --workflow=deploy-staging.yml --created="$SINCE" --json conclusion --jq 'length' 2>/dev/null || echo "0"

App deployments (24h): !SINCE=$(date --version 2>/dev/null | grep -q GNU && date -d '24 hours ago' -Iseconds || date -u -v-24H -Iseconds); gh run list --workflow=deploy-app-staging.yml --created="$SINCE" --json conclusion --jq 'length' 2>/dev/null || echo "0"

Railway CLI installed: !command -v railway >/dev/null 2>&1 && echo "✅ Yes" || echo "❌ No"

Railway usage: !railway usage 2>/dev/null || echo "Railway CLI not available"

Oldest deployment timestamp: !SINCE=$(date --version 2>/dev/null | grep -q GNU && date -d '24 hours ago' -Iseconds || date -u -v-24H -Iseconds); gh run list --workflow=deploy-staging.yml --created="$SINCE" --limit 1 --json createdAt --jq '.[0].createdAt' 2>/dev/null || echo ""

Recent deployment statuses: !SINCE=$(date --version 2>/dev/null | grep -q GNU && date -d '24 hours ago' -Iseconds || date -u -v-24H -Iseconds); gh run list --workflow=deploy-staging.yml --created="$SINCE" --limit 10 --json conclusion,createdAt,displayTitle --jq '.[] | "\(.conclusion) - \(.displayTitle) - \(.createdAt)"' 2>/dev/null || echo ""

What it does:

• Counts Vercel deployments in 24h rolling window (Marketing + App)
• Checks Railway compute usage (if CLI available)
• Calculates quota reset time from oldest deployment
• Predicts remaining quota after next deployment
• Provides deployment strategy based on quota status
• Analyzes recent deployment failure rate

Operating constraints:

• Vercel Limit — 100 deployments per 24 hours (rolling window)
• Warning Threshold — Alert when < 20 remaining
• Critical Threshold — Block when < 10 remaining
• Read-Only — Never modifies quotas or settings
• Non-Blocking — Always returns, even on errors

Dependencies:

• GitHub CLI installed and authenticated (gh auth login)
• Railway CLI optional (for compute usage tracking)
• Access to deploy-staging.yml and deploy-app-staging.yml workflows

1. Calculate total Vercel deployments:

   • Sum Marketing + App deployments from context
   • Calculate remaining: 100 - total_used
   • Determine status:
     • normal: >= 20 remaining (✅)
     • warning: 10-19 remaining (⚠️)
     • critical: < 10 remaining (🚨)

2. Display Vercel quota section:

   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
   Deployment Budget (24h rolling)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
   
   Vercel Deployments:
   
     Marketing (staging): {count}
     App (staging): {count}
   
     Total used: {total} / 100
     Remaining: {remaining}
   
     {status_emoji} {STATUS} - {remaining} deployments {available/remaining/left}
   

3. Display Railway usage (if CLI available):

   • If Railway CLI installed, show usage output
   • If not installed, show installation instructions:

     ⚠️  Railway CLI not installed
        Install: npm install -g @railway/cli
     

4. Calculate quota reset time:

   • Extract oldest deployment timestamp from context
   • Calculate reset time (24 hours from oldest)
   • Calculate time remaining until reset (hours and minutes)
   • Display:

     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
     Quota Reset Information
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
     
     Oldest deployment: {timestamp}
     Quota resets at: {reset_time}
     Time to reset: {hours}h {minutes}m