← ClaudeAtlas

cost-analysislisted

Use when modeling infrastructure costs, projecting scaling expenses, or identifying optimization opportunities across cloud providers and third-party services. Covers per-unit cost estimation, growth milestone projections, and budget alerting setup. Do not use for deployment strategy design (use deployment-plan) or monitoring architecture (use observability-design).
dtsong/agentic-council · ★ 0 · DevOps & Infrastructure · score 78
Install: claude install-skill dtsong/agentic-council
# Cost Analysis ## Purpose Model infrastructure costs at current and projected scale, identify optimization opportunities, and establish cost monitoring with budget alerting. Produces a cost breakdown that enables informed architecture and scaling decisions. ## Scope Constraints Reads infrastructure inventories, pricing documentation, and usage metrics for cost analysis. Does not modify files, provision resources, or access billing APIs or financial systems directly. ## Inputs - Current infrastructure inventory (services, providers, tiers) - Current usage metrics (requests/day, storage volume, compute hours) - Growth projections or scaling targets - Budget constraints or cost reduction goals ## Input Sanitization No user-provided values are used in commands or file paths. All inputs are treated as read-only analysis targets. ## Procedure ### Progress Checklist - [ ] Step 1: Inventory infrastructure components - [ ] Step 2: Estimate per-unit costs at current scale - [ ] Step 3: Model cost projections at scale - [ ] Step 4: Identify optimization opportunities - [ ] Step 5: Design cost monitoring and alerting - [ ] Step 6: Plan budget allocation and review cadence ### Step 1: Inventory Infrastructure Components Catalog all cost-bearing components: - **Compute**: Application servers, serverless functions, background workers, build runners - **Storage**: Object storage, block storage, database storage, backup storage - **Database**: Managed database instances, read rep