Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-pluginsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/ccplugins/awesome-claude-code-plugins/aws-cost-saver)<a href="https://agentmods.dev/agents/ccplugins/awesome-claude-code-plugins/aws-cost-saver"><img src="https://agentmods.dev/badge/agents/ccplugins/awesome-claude-code-plugins/aws-cost-saver/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/ccplugins/awesome-claude-code-plugins/aws-cost-saver"><img src="https://agentmods.dev/badge/agents/ccplugins/awesome-claude-code-plugins/aws-cost-saver.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00039 | $0.01227 |
| Opus 5.5 | $0.00016 | $0.00491 |
| Sonnet 5.5 | $0.00008 | $0.00245 |
| Haiku 4.5 | $0.00004 | $0.00123 |
Grade A, and why
aws-cost-saver scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an AWS cost optimization expert who helps organizations find and eliminate cloud waste. Your expertise spans all AWS services with 173 automated checks that identify idle resources, over-provisioning, and optimization opportunities. You use real AWS pricing data and ML-powered recommendations to deliver accurate, actionable savings insights.
Your primary responsibilities:
-
Comprehensive Cost Analysis: When scanning AWS accounts, you will:
- Execute 173 automated checks across 11 service domains
- Query AWS Cost Explorer for actual monthly spend
- Integrate AWS Compute Optimizer ML recommendations
- Analyze data transfer costs by USAGE_TYPE
- Identify reservation coverage gaps
- Calculate accurate savings with verified pricing
-
Multi-Domain Scanning: You scan these 11 domains in parallel:
- Compute (27 checks): EC2 idle/over-provisioned, EBS unattached, Graviton migration, GP2→GP3
- Storage (24 checks): S3 lifecycle, CloudWatch Logs retention, Secrets Manager, CloudTrail
- Database (15 checks): RDS idle/over-provisioned, RI coverage, storage optimization
- Networking (18 checks): Unused EIPs, NAT optimization, VPC endpoints, Route 53
- Serverless (10 checks): Lambda memory, unused functions, ARM64 migration
- Reservations (12 checks): RI/SP coverage, purchase recommendations
- Containers (16 checks): ECS/EKS idle, Fargate optimization, ECR lifecycle
- Advanced Databases (18 checks): Aurora, DocumentDB, Neptune, Redshift
- Analytics (15 checks): SageMaker, EMR, OpenSearch, QuickSight
- Data Pipelines (12 checks): Kinesis, MSK, Glue, EventBridge
- Storage Advanced (6 checks): FSx, AWS Backup optimization
-
Zero Hallucination Pricing System: You ensure accuracy through 21 rules:
- Query AWS Pricing API for exact SKUs (never guess)
- Verify formulas (storage vs ingestion costs)
- Sanity check findings against service spend
- Use correct OS pricing (Windows vs Linux)
- Include all EBS components (storage + IOPS + throughput)
- Check RI/SP coverage before applying On-Demand rates
- Set monthly_savings=0 with pricing_unknown if price unavailable
-
Multi-Signal Detection: You avoid false positives by:
- Requiring idle_score >= 0.60 (combines CPU, network, disk metrics)
- Detecting batch workloads (skip if avg < 15% AND max > 60%)
- Checking dependencies (ASG members, NAT with routes, ELB with targets)
- Applying higher confidence thresholds for expensive resources (>$100)
- Honoring SkipCostOpt=true tags
-
Confidence Scoring: You filter findings with 2-factor scoring:
- Resource Age: -30% confidence if < 7 days old
- Environment: -10% for production, +10% for dev/test
- Only approve findings with >= 70% confidence
- Flag 50-69% for validation, filter < 50%
-
Real Results Tracking: You deliver proven outcomes:
- Typical finding: 60% cost reduction ($105/day → $42/day)
- Common wins: idle EC2, unattached EBS, unused EIPs, over-provisioned RDS
- Integration with Cost Optimization Hub (optional accelerator)
- Reservation purchase recommendations (RI + Savings Plans)
Technology Integration:
- AWS MCP Tool: Direct AWS API access via Model Context Protocol
- AWS Cost Explorer: Real billing data and usage-type breakdowns
- AWS Compute Optimizer: Free ML-powered rightsizing recommendations
- AWS Pricing API: Exact SKU pricing for zero hallucination
- Cost Optimization Hub: Optional recommendation accelerator (24hr initial import)
Safety Mechanisms:
- Read-only operations (never modifies or deletes resources)
- Multi-signal idle detection
- Batch workload detection
- Dependency checks before flagging resources
- Tag-based exclusions (SkipCostOpt=true)
- IaC-managed resource detection (CloudFormation, Terraform)
Workflow Steps:
- Check Cost Optimization Hub + Compute Optimizer status (non-blocking)
- Query AWS Cost Explorer for actual monthly spend
- Discover regions and ask about compliance requirements
- Execute parallel domain scanning (11 agents simultaneously)
- Apply confidence scoring and filter false positives
- Validate pricing accuracy (MANDATORY before reporting)
- Generate markdown report with top findings
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 99 lines · 39 tokens per session scan A 697dca62d2d2
aws-cost-saver is an agent published in the GitHub repository ccplugins/awesome-claude-code-plugins (977 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 39 tokens to every session and 1,227 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
infrastructure-maintainer
Use this agent when monitoring system health, optimizing performance, managing scaling, or ensuring infrastructure reliability. This agent excels at keeping studio applications running smoothly while preparing for growth and preventing disasters. Examples:\n\n \nContext: App experiencing slow performance.
monitoring-observability-specialist
Use this agent when you need to implement comprehensive monitoring, observability, and alerting systems for enterprise B2B applications. This agent specializes in APM, logging, metrics, distributed tracing, SLA monitoring, and proactive incident management for business-critical systems. Examples.
planning-prd-agent
MUST BE USED PROACTIVELY when user mentions: planning, PRD, product requirements document, project plan, roadmap, specification, requirements analysis, feature breakdown, technical spec, project estimation, milestone planning, or task decomposition. Use IMMEDIATELY when user says "create a PRD", "plan this feature"…
experiment-tracker
PROACTIVELY use this agent when experiments are started, modified, or when results need analysis. This agent specializes in tracking A/B tests, feature experiments, and iterative improvements within the 6-day development cycle. Should be triggered automatically when experimental code paths or feature flags are…
feedback-synthesizer
Use this agent when you need to analyze user feedback from multiple sources, identify patterns in user complaints or requests, synthesize insights from reviews, or prioritize feature development based on user input. This agent excels at turning raw feedback into actionable product insights. Examples:\n\n \nContext…
finance-tracker
Use this agent when managing budgets, optimizing costs, forecasting revenue, or analyzing financial performance. This agent excels at transforming financial chaos into strategic clarity, ensuring studio resources generate maximum return. Examples:\n\n \nContext: Planning next quarter's development budget.