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/prajapatimehul/claude-aws-cost-saverWrote 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/commands/prajapatimehul/claude-aws-cost-saver/scan)<a href="https://agentmods.dev/commands/prajapatimehul/claude-aws-cost-saver/scan"><img src="https://agentmods.dev/badge/commands/prajapatimehul/claude-aws-cost-saver/scan/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/commands/prajapatimehul/claude-aws-cost-saver/scan"><img src="https://agentmods.dev/badge/commands/prajapatimehul/claude-aws-cost-saver/scan.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.00006 | $0.03577 |
| Opus 5 | $0.00003 | $0.01788 |
| Sonnet 5 | $0.00001 | $0.00715 |
| Haiku 4.5 | $0.00001 | $0.00358 |
Grade A, and why
scan 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 11d 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 — 398 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Cost Optimization Scan
Step 0: Ask for AWS Profile
If a profile name was passed as an argument ($ARGUMENTS), use it and skip the question.
Otherwise, ask the user which AWS profile to use:
{
"questions": [{
"header": "AWS Profile",
"question": "Which AWS profile should I use for the scan?",
"multiSelect": false,
"options": [
{"label": "default", "description": "Use default AWS credentials"},
{"label": "Enter profile name", "description": "I'll type my profile name"}
]
}]
}
If user selects "Enter profile name" or "Other", ask them to type the profile name.
Store the profile name for all subsequent AWS commands.
Authentication: AWS commands work with any valid AWS credentials:
- SSO profile:
--profile your-sso-profile - Named profile:
--profile your-profile - Environment variables:
AWS_ACCESS_KEY_ID,AWS_SECRET_ACCESS_KEY - IAM role (EC2/Lambda): automatic
Step 1: Discover Account
aws sts get-caller-identity --profile {profile}
Extract:
- Account ID → use in report header
- Profile name → use for file naming:
reports/findings_{profile}.json
Step 2: Find Active Regions
# Get all regions
aws ec2 describe-regions --profile {profile} --query 'Regions[].RegionName' --output json
# Check which have EC2 instances (quick check)
aws ec2 describe-instances --profile {profile} --query 'Reservations[].Instances[0].Placement.AvailabilityZone' --output text
Only scan regions with resources.
Step 3: Ask Compliance
Use AskUserQuestion:
{
"questions": [{
"header": "Compliance",
"question": "Which compliance requirements apply?",
"multiSelect": true,
"options": [
{"label": "HIPAA", "description": "Healthcare - skip PHI resources"},
{"label": "SOC2", "description": "Audit - preserve all logs"},
{"label": "PCI-DSS", "description": "Payments - skip payment infra"},
{"label": "None", "description": "No compliance requirements"}
]
}]
}
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.
- 11d ago First seen · 398 lines · 6 tokens per session scan A 8c621c8afb29
scan is a command published in the GitHub repository prajapatimehul/claude-aws-cost-saver (22 stars, last pushed 2mo ago), licensed MIT. It adds 6 tokens to every session and 3,577 once invoked, about $0.0000 per session on Opus 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 commands, from other repositories
cost-optimize
You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, and GCP.
cfo
Chief Financial Officer review — cloud cost optimization, resource efficiency, billing logic, compute waste.
datadog
Set up and troubleshoot Datadog — Agent deployment on Kubernetes, APM instrumentation, Log Management, Monitors, Dashboards, SLOs, Synthetic tests, and live incident investigation using the Datadog MCP server. Covers Terraform-managed Datadog resources.
fluxcd
FluxCD entry point — routes to the right workflow based on what you need. Live cluster issue → structured 5-workflow debug trace. Repo health check → 6-phase audit (discovery, validation, API compliance, best practices, security). Helm chart review → helmchart. Starts by asking one question to confirm the right mode.
linkerd
Linkerd-specific diagnostics — mTLS verification, proxy injection issues, authorization policy debugging, traffic management, and multi-cluster connectivity problems.
aws-profile
AWS profile management for MCP servers — discover profiles across SSO, Granted, and assumed-role chains, check credential TTL, switch profiles across VS Code and Claude Code MCP configs, and scan AWS Organization accounts.