Token导航 LogoToken导航

Agent Skill · 研究检索

aws-cost-optimizer(AWS cost 优化器)

用于辅助云资源、部署、容器、基础设施和运维自动化任务。它适合让 Agent 检查配置、整理部署步骤、分析资源状态、生成排障思路或辅助云服务接入。使用时需要明确目标环境、账号权限、区域和资源组,区分本地测试与生产操作;涉及删除资源、重启服务、修改网络或权限配置时,应先确认影响范围。

aws-cost-optimizer 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 68,654。

总安装 225周安装 9GitHub Stars 27下载 73核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:aws-cost-optimizer(AWS cost 优化器)
来源仓库:https://github.com/armanzeroeight/fastagent-plugins
仓库路径:skills/aws-cost-optimizer
安装命令:
npx skills add https://github.com/armanzeroeight/fastagent-plugins --skill aws-cost-optimizer
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/armanzeroeight/fastagent-plugins --skill aws-cost-optimizer

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于 AWS 成本分析与优化建议生成。aws-cost-optimizer 属于研究检索类 Skill,可作为该场景下的辅助能力补充。基于 Cost Explorer 数据识别高消耗服务并提出降本措施。支持 EC2 实例调优、预留实例采购与闲置资源清理建议。

安装方式:通过 npx skills add 命令从指定 GitHub 仓库添加。使用前应确认账单数据权限与区域覆盖范围,防止遗漏关键支出项。

来源仓库内路径:skills/aws-cost-optimizer

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/armanzeroeight/fastagent-plugins --skill aws-c…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

aws-cost-optimizer 怎么安装?

在终端执行 npx skills add https://github.com/armanzeroeight/fastagent-plugins --skill aws-cost-optimi…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

aws-cost-optimizer 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

aws-cost-optimizer 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

aws-cost-optimizer 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

aws-cost-optimizer 用的人多吗?

公开数据是累计安装 225 次,近一周安装 9 次,下载 73 次,GitHub 27 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

aws-cost-optimizer 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
aws-cost-optimizer

AWS cost 优化器 · 本页

22527需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

AWS Cost Optimizer

Analyze and optimize AWS costs with actionable recommendations.

Quick Start

Review Cost Explorer, identify top costs, right-size instances, use Reserved Instances, delete unused resources.

Instructions

Cost Analysis Process

  1. Identify cost drivers
  2. Analyze usage patterns
  3. Recommend optimizations
  4. Estimate savings
  5. Implement changes

Using AWS Cost Explorer

Access Cost Explorer:

  • AWS Console → Billing → Cost Explorer
  • View costs by service, region, tag

Key metrics to check:

  • Monthly costs by service
  • Cost trends over time
  • Unused or underutilized resources
  • Data transfer costs

EC2 Cost Optimization

Right-sizing instances:

Check utilization:

# Get CloudWatch metrics
aws cloudwatch get-metric-statistics \
  --namespace AWS/EC2 \
  --metric-name CPUUtilization \
  --dimensions Name=InstanceId,Value=i-1234567890abcdef0 \
  --start-time 2024-01-01T00:00:00Z \
  --end-time 2024-01-31T23:59:59Z \
  --period 3600 \
  --statistics Average

Recommendations:

  • CPU < 20%: Downsize instance type
  • CPU > 80%: Upsize or add instances
  • Memory < 50%: Consider smaller instance

Reserved Instances:

  • 1-year: ~30-40% savings
  • 3-year: ~50-70% savings
  • Best for predictable workloads

Savings Plans:

  • More flexible than Reserved Instances
  • Commit to $/hour usage
  • Apply across instance families

Spot Instances:

  • Up to 90% savings
  • For fault-tolerant workloads
  • Batch processing, CI/CD, testing

Stop unused instances:

# Find stopped instances
aws ec2 describe-instances \
  --filters "Name=instance-state-name,Values=stopped" \
  --query 'Reservations[].Instances[].[InstanceId,Tags[?Key==`Name`].Value|[0]]'

# Terminate if not needed
aws ec2 terminate-instances --instance-ids i-1234567890abcdef0

S3 Cost Optimization

Lifecycle policies:

{
  "Rules": [{
    "Id": "Archive old data",
    "Status": "Enabled",
    "Transitions": [
      {
        "Days": 30,
        "StorageClass": "STANDARD_IA"
      },
      {
        "Days": 90,
        "StorageClass": "GLACIER"
      }
    ],
    "Expiration": {
      "Days": 365
    }
  }]
}

Storage classes:

  • Standard: Frequent access
  • Standard-IA: Infrequent access (30+ days)
  • Glacier: Archive (90+ days)
  • Glacier Deep Archive: Long-term archive

Delete incomplete multipart uploads:

aws s3api list-multipart-uploads --bucket my-bucket
# Set lifecycle rule to abort after 7 days

Analyze storage:

# Get bucket size
aws s3 ls s3://my-bucket --recursive --summarize

RDS Cost Optimization

Right-size databases:

  • Check CPU, memory, IOPS utilization
  • Downsize if consistently low
  • Use Aurora Serverless for variable workloads

Reserved Instances:

  • 1-year: ~30-40% savings
  • 3-year: ~50-60% savings

Stop dev/test databases:

# Stop RDS instance
aws rds stop-db-instance --db-instance-identifier mydb

# Start when needed
aws rds start-db-instance --db-instance-identifier mydb

Delete old snapshots:

# List snapshots
aws rds describe-db-snapshots --query 'DBSnapshots[?SnapshotCreateTime<`2023-01-01`]'

# Delete old snapshots
aws rds delete-db-snapshot --db-snapshot-identifier snapshot-id

Data Transfer Costs

Reduce data transfer:

  • Use CloudFront for content delivery
  • Keep data in same region
  • Use VPC endpoints for AWS services
  • Compress data before transfer

VPC endpoints:

# Create S3 VPC endpoint (no data transfer charges)
aws ec2 create-vpc-endpoint \
  --vpc-id vpc-12345678 \
  --service-name com.amazonaws.us-east-1.s3 \
  --route-table-ids rtb-12345678

EBS Cost Optimization

Delete unattached volumes:

# Find unattached volumes
aws ec2 describe-volumes \
  --filters "Name=status,Values=available" \
  --query 'Volumes[].[VolumeId,Size,VolumeType]'

# Delete if not needed
aws ec2 delete-volume --volume-id vol-1234567890abcdef0

Delete old snapshots:

# List old snapshots
aws ec2 describe-snapshots --owner-ids self \
  --query 'Snapshots[?StartTime<`2023-01-01`]'

# Delete
aws ec2 delete-snapshot --snapshot-id snap-1234567890abcdef0

Use gp3 instead of gp2:

  • gp3 is 20% cheaper
  • Better performance
  • Migrate existing volumes

Lambda Cost Optimization

Optimize memory allocation:

  • More memory = faster execution = lower cost
  • Test different memory settings
  • Use AWS Lambda Power Tuning tool

Reduce cold starts:

  • Use provisioned concurrency (if needed)
  • Keep functions warm with scheduled events
  • Minimize dependencies

Monitor invocations:

# Get Lambda metrics
aws cloudwatch get-metric-statistics \
  --namespace AWS/Lambda \
  --metric-name Invocations \
  --dimensions Name=FunctionName,Value=my-function \
  --start-time 2024-01-01T00:00:00Z \
  --end-time 2024-01-31T23:59:59Z \
  --period 86400 \
  --statistics Sum

CloudWatch Costs

Reduce log retention:

# Set log retention to 7 days
aws logs put-retention-policy \
  --log-group-name /aws/lambda/my-function \
  --retention-in-days 7

Delete unused log groups:

# List log groups
aws logs describe-log-groups

# Delete
aws logs delete-log-group --log-group-name /aws/lambda/old-function

Unused Resources

Find unused resources:

Elastic IPs not attached:

aws ec2 describe-addresses \
  --query 'Addresses[?AssociationId==null]'

Load balancers with no targets:

aws elbv2 describe-load-balancers
aws elbv2 describe-target-health --target-group-arn arn

NAT Gateways with low traffic:

# Check CloudWatch metrics for BytesOutToDestination

Cost Optimization Checklist

Compute:

  • Right-size EC2 instances
  • Use Reserved Instances for predictable workloads
  • Use Spot Instances for fault-tolerant workloads
  • Stop/terminate unused instances
  • Implement auto-scaling

Storage:

  • Implement S3 lifecycle policies
  • Delete old EBS snapshots
  • Delete unattached EBS volumes
  • Use appropriate S3 storage classes
  • Delete incomplete multipart uploads

Database:

  • Right-size RDS instances
  • Use Reserved Instances
  • Stop dev/test databases when not in use
  • Delete old RDS snapshots
  • Consider Aurora Serverless

Networking:

  • Use CloudFront to reduce data transfer
  • Delete unused Elastic IPs
  • Use VPC endpoints
  • Review NAT Gateway usage

Monitoring:

  • Reduce CloudWatch log retention
  • Delete unused log groups
  • Review custom metrics

General:

  • Enable AWS Cost Anomaly Detection
  • Set up billing alerts
  • Use AWS Budgets
  • Tag resources for cost allocation
  • Review Cost Explorer regularly

Savings Estimation

Reserved Instances:

  • 1-year, no upfront: ~30% savings
  • 1-year, all upfront: ~40% savings
  • 3-year, all upfront: ~60% savings

Spot Instances:

  • 70-90% savings vs On-Demand

S3 Lifecycle:

  • Standard-IA: ~50% cheaper than Standard
  • Glacier: ~80% cheaper than Standard

Right-sizing:

  • Typical savings: 20-40% on oversized instances

Tools and Commands

AWS Cost Explorer:

  • View costs by service, region, tag
  • Forecast future costs
  • Identify cost anomalies

AWS Budgets:

# Create budget
aws budgets create-budget \
  --account-id 123456789012 \
  --budget file://budget.json

AWS Trusted Advisor:

  • Cost optimization recommendations
  • Underutilized resources
  • Idle resources

Third-party tools:

  • CloudHealth
  • CloudCheckr
  • Spot.io

Best Practices

Tagging strategy:

  • Tag all resources
  • Use tags for cost allocation
  • Common tags: Environment, Project, Owner, CostCenter

Regular reviews:

  • Weekly: Check for anomalies
  • Monthly: Review Cost Explorer
  • Quarterly: Optimize Reserved Instances

Automation:

  • Auto-stop dev instances at night
  • Auto-delete old snapshots
  • Auto-scale based on demand

Monitoring:

  • Set up billing alerts
  • Use AWS Budgets
  • Enable Cost Anomaly Detection

平台分布

Codex

38.6%
按下载量换算28

Claude

27.89%
按下载量换算20

Cursor

20.08%
按下载量换算15

Gemini CLI

8.39%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills