| name | costs |
| description | API spend breakdown and cost-optimization analysis |
| when_to_use | Use when Abdout asks where the money goes — API and infra spend breakdown with cost-optimization analysis across Vercel, Neon, AWS, and the Anthropic plan, honoring the subscription-only posture. Triggers on: costs, spend, how much are we paying, cost optimization, budget check. |
| argument-hint | [monthly|<service>] |
| model | sonnet |
API spend breakdown and cost optimization analysis.
Arguments: $ARGUMENTS (optional: "monthly" for full report, or specific service like "vercel", "neon", "stripe")
Steps:
- Gather cost data:
- Claude Max subscription: $200/mo (fixed)
- Vercel: Check usage tier and bandwidth (vercel MCP)
- Neon: Check branch count, compute hours (neon MCP)
- Stripe: Calculate transaction fees from recent volume (stripe MCP)
- Domains: Estimate from known registrations
- Calculate total monthly spend
- Compare against budget (~$500/mo burn, $5K capital = 10 months runway)
- Identify optimization opportunities:
- Can any Vercel project stay on free tier?
- Are there stale Neon branches to delete?
- Can Stripe fees be reduced with annual billing?
- Are we using Claude API efficiently?
- Project next month's costs based on trends
- Output: cost table, trend, optimizations, recommendation
Reference: .claude/agents/ops.md for cost structure
Reference: .claude/agents/revenue.md for revenue context