- name
Analyze AWS resources used in the app (IaC files and/or resources in a target account/region) and optimize costs - creating GitHub issues for identified optimizations.
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add github/awesome-copilot --skill aws-cost-optimize -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add github/awesome-copilot --skill aws-cost-optimize -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add github/awesome-copilot --skill aws-cost-optimize -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add github/awesome-copilot --skill aws-cost-optimize -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/github/awesome-copilot/tree/HEAD/skills/aws-cost-optimizeFrom the publisher
This workflow analyzes Infrastructure-as-Code (IaC) files and AWS resources to generate cost optimization recommendations. It creates individual GitHub issues for each optimization opportunity plus one EPIC issue to coordinate implementation, enabling efficient tracking and execution of cost savings initiatives.
aws sts get-caller-identity succeeds)Action: Retrieve cost optimization best practices before analysis
Tools: fetch to retrieve AWS documentation
Process:
https://docs.aws.amazon.com/cost-management/latest/userguide/cost-optimization-best-practices.htmlAction: Dynamically discover and analyze AWS resources and configurations Tools: AWS CLI + Local file system access Process:
Account & Region Discovery:
aws sts get-caller-identity to confirm accountaws configure get region to determine default regionResource Discovery (per region):
aws ec2 describe-instances --query 'Reservations[].Instances[].[InstanceId,InstanceType,State.Name,Tags]'aws rds describe-db-instances --query 'DBInstances[].[DBInstanceIdentifier,DBInstanceClass,Engine,MultiAZ]'aws lambda list-functions --query 'Functions[].[FunctionName,Runtime,MemorySize,Architectures]'aws ecs list-clusters then aws ecs describe-servicesaws s3api list-buckets --query 'Buckets[].Name'aws elasticache describe-cache-clustersaws ec2 describe-nat-gatewaysaws elbv2 describe-load-balancersIaC Detection:
**/*.tf, **/*.yaml (CloudFormation/SAM), **/*.json (CloudFormation), **/cdk.json, lib/**/*.ts (CDK)Action: Gather utilization data and verify actual resource costs Tools: AWS CLI (CloudWatch, Cost Explorer) Process:
CloudWatch Metrics (last 7 days):
# EC2 CPU utilization
aws cloudwatch get-metric-statistics \
--namespace AWS/EC2 --metric-name CPUUtilization \
--dimensions Name=InstanceId,Value=<id> \
--start-time $(date -u -d '7 days ago' +%Y-%m-%dT%H:%M:%SZ) \
--end-time $(date -u +%Y-%m-%dT%H:%M:%SZ) \
--period 3600 --statistics Average
# Lambda duration
aws cloudwatch get-metric-statistics \
--namespace AWS/Lambda --metric-name Duration \
--dimensions Name=FunctionName,Value=<name> \
--start-time $(date -u -d '7 days ago' +%Y-%m-%dT%H:%M:%SZ) \
--end-time $(date -u +%Y-%m-%dT%H:%M:%SZ) \
--period 86400 --statistics Average,Maximum
AWS Cost Explorer:
aws ce get-cost-and-usage \
--time-period Start=$(date -u -d '30 days ago' +%Y-%m-%d),End=$(date -u +%Y-%m-%d) \
--granularity MONTHLY --metrics BlendedCost \
--group-by Type=DIMENSION,Key=SERVICE
Calculate Baseline Metrics: CPU/Memory averages, Lambda invocation rates, data transfer patterns, and a realistic current monthly total.
Action: Analyze resources to identify optimization opportunities Process:
Apply Optimization Patterns:
Compute:
arm64 (20% cheaper)Database:
Storage:
Network:
Calculate Priority Score:
Priority Score = (Value Score × Monthly Savings) / (Risk Score × Implementation Days)
High: Score > 20 | Medium: Score 5-20 | Low: Score < 5
Action: Present summary and get approval before creating GitHub issues
🎯 AWS Cost Optimization Summary
📊 Analysis Results:
• Total Resources Analyzed: X
• Current Monthly Cost: $X
• Potential Monthly Savings: $Y
• Optimization Opportunities: Z
• High Priority Items: N
🏆 Recommendations:
1. [Resource]: [Current] → [Target] = $X/month savings - [Risk] | [Effort]
...
💡 This will create Y individual GitHub issues + 1 EPIC issue.
❓ Proceed with creating GitHub issues? (y/n)
Wait for user confirmation before proceeding.
Action: Create separate GitHub issues for each optimization. Label with "cost-optimization" (green) and "aws" (orange).
Title: [COST-OPT] [Resource Type] - [Brief Description] - $X/month savings
Body:
## 💰 Cost Optimization: [Brief Title]
**Monthly Savings**: $X | **Risk Level**: [Low/Medium/High] | **Effort**: X days
### 📋 Description
[Clear explanation of the optimization and why it's needed]
### 🔧 Implementation
**IaC Files Detected**: [Yes/No]
```bash
# IaC modification (preferred) or AWS CLI fallback
```
### 📊 Evidence
- Current Configuration: [details]
- Usage Pattern: [evidence from CloudWatch]
- Cost Impact: $X/month → $Y/month
### ✅ Validation Steps
- [ ] Test in non-production environment
- [ ] Verify no performance degradation via CloudWatch
- [ ] Confirm cost reduction in AWS Cost Explorer
### ⚠️ Risks & Considerations
- [Risk and mitigation]
**Priority Score**: X | **Value**: X/10 | **Risk**: X/10
Action: Create master tracking issue. Label with "cost-optimization" (green), "aws" (orange), "epic" (purple).
Title: [EPIC] AWS Cost Optimization Initiative - $X/month potential savings
Body: Executive summary with account/region details, Mermaid architecture diagram of current resources, prioritized checklist linking all individual issues (High → Medium → Low), progress tracking, and success criteria (>80% of estimated savings realized, no performance degradation).
aws configure© 2026 Skills Rack.
---name: aws-cost-optimizedescription: Analyze AWS resources used in the app (IaC files and/or resources in a target account/region) and optimize…---# skills/aws-cost-optimize/SKILL.mdFAQ
Download skills/aws-cost-optimize/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/github/awesome-copilot.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.