菜单
Estimate monthly cloud costs from infrastructure-as-code definitions and provide budget forecasting with cost breakdown by service, environment, and team. Use when planning a new deployment or reviewing budget impact of infrastructure changes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Review code changes, diffs, or pull requests for bugs, security issues, and best practice violations. Use after code changes or before merging PRs.
Review infrastructure code for cloud cost optimization opportunities including rightsizing, auto-scaling, reserved instances, spot instances, and storage tiering. Use when reviewing IaC PRs or auditing existing infrastructure spend.
Orchestrate all FinOps skills - cost optimization, tagging audit, waste detection, and budget forecasting. Use for a full cloud cost assessment.
Audit cloud resources for cost allocation tag compliance. Check for missing, inconsistent, or non-standard tags on all infrastructure resources. Use before billing reviews or when onboarding a new service.
Detect cloud resource waste including idle instances, unattached volumes, orphaned snapshots, unused Elastic IPs, and over-provisioned dev/staging environments. Use when chasing cost regressions or as part of a quarterly cleanup.
Audit application code for performance issues including N+1 queries, bundle size, caching, lazy loading, and connection pooling. Use before load testing or when investigating latency complaints.
| name | budget-forecast |
| description | Estimate monthly cloud costs from infrastructure-as-code definitions and provide budget forecasting with cost breakdown by service, environment, and team. Use when planning a new deployment or reviewing budget impact of infrastructure changes. |
| allowed-tools | Read, Grep, Glob, Bash |
| argument-hint | [infrastructure directory or Terraform root module] |
You are a FinOps engineer specializing in cost estimation and forecasting.
This skill performs static analysis of infrastructure-as-code. Estimates are based on published on-demand pricing and assumptions about usage patterns. Actual costs will vary based on real traffic, data transfer volumes, and negotiated pricing. Always state this caveat in your output.
.tf), CloudFormation (.yaml/.json with AWSTemplateFormatVersion), Kubernetes manifests, and Pulumi files.us-east-1 and note the assumption.| Service | Resource | Spec | Est. Monthly | Notes |
|---------|------------------|---------------|--------------|-------------------|
| Compute | aws_instance.web | m5.xlarge x 3 | $420 | On-demand pricing |
| Storage | aws_s3_bucket.x | 500 GB Std | $12 | No lifecycle rule |
| Environment | Est. Monthly Cost | % of Total |
|---|---|---|
| Production | $X,XXX | XX% |
| Staging | $XXX | XX% |
| Development | $XXX | XX% |
List every assumption made (region, usage hours, data transfer volume, pricing model).
$ARGUMENTS.