Analisa recursos da AWS e arquivos de IaC para identificar oportunidades de economia de custos e cria issues correspondentes no GitHub para implementação.
- Estrelas no GitHub
- 41.038
- Arquivos
- 1
- Último commit
- 11 de nov. de 2026
- Licença
- MIT
- Ferramentas permitidas
- —
O que a skill aws-cost-optimize faz?
Analisa recursos da AWS e arquivos de IaC para identificar oportunidades de economia de custos e cria issues correspondentes no GitHub para implementação.
Resumo gerado a partir do SKILL.md da skill.
Sobre a skill aws-cost-optimize
Identificar formas de reduzir gastos com nuvem através da análise de infraestrutura é o que este SKILL permite para engenheiros de DevOps e arquitetos de nuvem. Ele examina seu ambiente AWS escaneando recursos ativos como instâncias EC2, bancos de dados RDS, funções Lambda e buckets S3, juntamente com seus arquivos de Infrastructure-as-Code, como Terraform ou CloudFormation. Ao combinar métricas de uso em tempo real do CloudWatch com dados históricos de faturamento do Cost Explorer, a ferramenta identifica padrões específicos onde você está com excesso de provisionamento ou utilizando configurações ineficientes.
Assim que a análise é concluída, o SKILL apresenta um resumo de possíveis economias mensais e níveis de risco para sua aprovação. Após a confirmação, ele gera automaticamente um conjunto estruturado de issues no GitHub para rastrear o trabalho. Isso inclui tarefas individuais para cada otimização específica e uma issue master do tipo EPIC para coordenar toda a iniciativa de redução de custos. Ele depende de um AWS CLI configurado e de um MCP server do GitHub conectado para realizar essas ações.
O que um agente pode fazer com ela
- 1Automatizar auditorias de custos de nuvemUm engenheiro pode solicitar um scan completo de sua conta AWS para encontrar recursos subutilizados e gerar tarefas acionáveis.
- 2Converter economias manuais em tarefas rastreáveisUm desenvolvedor pode transformar melhorias de infraestrutura identificadas em um fluxo de trabalho gerenciado dentro de um repositório do GitHub.
- 3Validar infraestrutura contra as melhores práticasUsuários podem garantir que sua configuração atual da AWS esteja alinhada com a documentação oficial de gerenciamento de custos e com os pilares de arquitetura bem estruturada.
Escrito a partir do SKILL.md da skill. Cada caso de uso é verificado com uma citação dele.
Como instalar a skill aws-cost-optimize
Cada comando copia a pasta da skill para o diretório de skills do cliente. Reinicie o cliente ou inicie uma nova sessão para carregá-la.Instalar a skill aws-cost-optimize no Claude Code
~/.claude/skills/aws-cost-optimize/SKILL.md
$ npx degit github/awesome-copilot/skills/aws-cost-optimize ~/.claude/skills/aws-cost-optimizeInstalar a skill aws-cost-optimize no Claude Code (project)
.claude/skills/aws-cost-optimize/SKILL.md
$ npx degit github/awesome-copilot/skills/aws-cost-optimize .claude/skills/aws-cost-optimizeInstalar a skill aws-cost-optimize no Codex
~/.agents/skills/aws-cost-optimize/SKILL.md
$ npx degit github/awesome-copilot/skills/aws-cost-optimize ~/.agents/skills/aws-cost-optimizeInstalar a skill aws-cost-optimize no Gemini CLI
~/.gemini/skills/aws-cost-optimize/SKILL.md
$ npx degit github/awesome-copilot/skills/aws-cost-optimize ~/.gemini/skills/aws-cost-optimizeInstalar a skill aws-cost-optimize no Claude.ai
npx degit github/awesome-copilot/skills/aws-cost-optimize aws-cost-optimize && zip -r aws-cost-optimize.zip aws-cost-optimize # claude.ai → Customize → Skills → + → Create skill → Upload a skill → aws-cost-optimize.zip
Verificações automatizadas
Executado em 15 de nov. de 2026Relatório completo →Passou nas nossas verificações automáticas. Não é uma auditoria de segurança: leia os scripts antes de deixar um agente executá-los. Como as verificações funcionam · O que corrigir para ganhar mais pontos
- Repositório de origem vinculado e acessívelgithub/awesome-copilot/skills/aws-cost-optimize is public and reachablegithub.com/github/awesome-copilot/tree/HEAD/skills/aws-cost- ↗Passou
- Licença de código aberto (OSI)MITspdx.org/licenses/MIT.html ↗Passou
- Commit ou release no último anoLast commit 2026-11-11github.com/github/awesome-copilot/commits ↗Passou
- Sem baixar e executar nem roubo de credenciais nos scriptsNo scripts in the skill folderPassou
- Sem instruções ocultas no SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/github/awesome-copilot/blob/HEAD/skills/aws-cost- ↗Passou
- Ferramentas pré-aprovadas são restritasNo pre-approved tools; the agent asks before using onegithub.com/github/awesome-copilot/blob/HEAD/skills/aws-cost- ↗Passou
- O SKILL.md segue o formato Agent Skillsthe description does not say when to use the skillgithub.com/github/awesome-copilot/blob/HEAD/skills/aws-cost- ↗Problema encontrado
SKILL.md
Ver no GitHubAWS Cost Optimize
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.
Prerequisites
- AWS CLI configured and authenticated (
aws sts get-caller-identitysucceeds) - GitHub MCP server configured and authenticated
- Target GitHub repository identified
- AWS resources deployed (IaC files optional but helpful)
Workflow Steps
Step 1: Get AWS Cost Optimization Best Practices
Action: Retrieve cost optimization best practices before analysis
Tools: fetch to retrieve AWS documentation
Process:
- Load Best Practices:
- Fetch
https://docs.aws.amazon.com/cost-management/latest/userguide/cost-optimization-best-practices.html - Fetch the AWS Well-Architected Cost Optimization pillar summary
- Use these practices to inform subsequent analysis and recommendations
- Fetch
Step 2: Discover AWS Infrastructure
Action: Dynamically discover and analyze AWS resources and configurations Tools: AWS CLI + Local file system access Process:
-
Account & Region Discovery:
- Execute
aws sts get-caller-identityto confirm account - Execute
aws configure get regionto determine default region
- Execute
-
Resource Discovery (per region):
- EC2 instances:
aws ec2 describe-instances --query 'Reservations[].Instances[].[InstanceId,InstanceType,State.Name,Tags]' - RDS instances:
aws rds describe-db-instances --query 'DBInstances[].[DBInstanceIdentifier,DBInstanceClass,Engine,MultiAZ]' - Lambda functions:
aws lambda list-functions --query 'Functions[].[FunctionName,Runtime,MemorySize,Architectures]' - ECS clusters/services:
aws ecs list-clustersthenaws ecs describe-services - S3 buckets:
aws s3api list-buckets --query 'Buckets[].Name' - ElastiCache clusters:
aws elasticache describe-cache-clusters - NAT Gateways:
aws ec2 describe-nat-gateways - Load Balancers:
aws elbv2 describe-load-balancers
- EC2 instances:
-
IaC Detection:
- Scan for IaC files:
**/*.tf,**/*.yaml(CloudFormation/SAM),**/*.json(CloudFormation),**/cdk.json,lib/**/*.ts(CDK) - Parse resource definitions to understand intended configurations
- Do NOT use application code files — only IaC files as the source of truth
- If no IaC files found: STOP and report to user
- Scan for IaC files:
Step 3: Collect Usage Metrics & Validate Current Costs
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.
Step 4: Generate Cost Optimization Recommendations
Action: Analyze resources to identify optimization opportunities Process:
-
Apply Optimization Patterns:
Compute:
- EC2: Right-size based on CPU/memory (<20% average → downsize), convert On-Demand to Savings Plans, migrate to Graviton/ARM (up to 40% cheaper)
- Lambda: Reduce memory for idle functions, switch to
arm64(20% cheaper) - ECS/EKS: Use Fargate Spot for dev/batch workloads
Database:
- RDS: Right-size instance class, convert single-AZ for dev, use Aurora Serverless v2 for variable load
- DynamoDB: Switch Provisioned → On-Demand for unpredictable traffic
- ElastiCache: Right-size node type based on memory utilization
Storage:
- S3: Lifecycle policies (Standard → Standard-IA after 30d → Glacier after 90d), enable Intelligent-Tiering
- EBS: Delete unattached volumes, convert gp2 → gp3 (same performance, 20% cheaper)
Network:
- Consolidate NAT Gateways for non-production environments
- Use VPC endpoints for S3/DynamoDB to avoid NAT Gateway charges
-
Calculate Priority Score:
Priority Score = (Value Score × Monthly Savings) / (Risk Score × Implementation Days) High: Score > 20 | Medium: Score 5-20 | Low: Score < 5
Step 5: User Confirmation
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.
Step 6: Create Individual Optimization Issues
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
Step 7: Create EPIC Coordinating Issue
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).
Error Handling
- AWS Authentication Failure: Guide through
aws configure - No Resources Found: Create informational issue about AWS resource deployment
- Insufficient Permissions: List required IAM read-only permissions
- GitHub Creation Failure: Output formatted recommendations to console
- Cost Explorer Not Enabled: Guide user to enable in AWS Console
Success Criteria
- ✅ All cost estimates verified against actual configurations and AWS pricing
- ✅ Individual GitHub issues created for each optimization
- ✅ EPIC issue provides comprehensive coordination and tracking
- ✅ All recommendations include specific AWS CLI or IaC commands
- ✅ User confirmation obtained before creating issues
Arquivos desta skill
1Perguntas sobre a skill aws-cost-optimize
Como instalo a skill aws-cost-optimize no Claude Code?
Execute npx degit github/awesome-copilot/skills/aws-cost-optimize ~/.claude/skills/aws-cost-optimize. O Claude Code carrega skills de ~/.claude/skills (todos os projetos) ou .claude/skills (um projeto) e usa uma skill quando a descrição dela corresponde à tarefa.
Quais clientes podem usar a skill aws-cost-optimize?
Qualquer cliente que leia o formato Agent Skills: Claude Code, Codex, Gemini CLI e claude.ai (envie como ZIP). Scripts da skill são executados apenas onde o cliente permite execução de código.
Como a ferramenta identifica oportunidades de otimização?
Ela recupera as melhores práticas da AWS, descobre a infraestrutura via CLI e arquivos de IaC, coleta métricas de uso do CloudWatch e aplica padrões de otimização específicos para recursos de computação, banco de dados, armazenamento e rede.