[skill-name-kebab-case]

Detects AWS cost anomalies using Cost Explorer metrics and EC2 instance analysis.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/schoolofdevops/401 --skill skill-name-kebab-case-schoolofdevops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: [skill-name-kebab-case]
Source: https://github.com/schoolofdevops/401/tree/main/modules/module-07-skills/starter/track-b-finops
Command: npx skills add https://github.com/schoolofdevops/401 --skill skill-name-kebab-case-schoolofdevops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Unexpected AWS billing spikes and idle resources often go unnoticed until the monthly invoice arrives. This Skill provides a structured workflow for detecting cost anomalies, identifying unused EC2 resources, and escalating findings before they become budget overruns. ## Core Features & Use Cases - Cost Anomaly Detection: Queries AWS Cost Explorer with aws ce get-cost-and-usage to compare daily spend against a baseline and flag spikes above a defined threshold. - Unused Resource Identification: Uses aws ec2 describe-instances to find instances idle beyond a set number of hours. - Safe Escalation Workflow: Defines explicit NEVER DO rules (no terminating instances, no modifying Reserved Instances) plus rollback and verification procedures. - Use Case: A FinOps engineer notices a 60% daily cost spike, runs the Skill in mock mode to diagnose whether a mismatched EC2 instance type caused it, and escalates with a documented report. ## Quick Start Ask the assistant to analyze daily AWS costs in your region for anomalies against the baseline using the configured EC2 instance and report any unused resources.

Frequently Asked Questions about [skill-name-kebab-case]

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect AWS cost anomalies with Cost Explorer?

Use aws ce get-cost-and-usage to retrieve daily spend, then compare it against a baseline. This Skill flags anomalies when daily cost exceeds 1.5 times the baseline and reports the contributing usage dimensions.

How to find unused EC2 instances with AWS CLI?

Run aws ec2 describe-instances to inspect instance state and utilization signals. The Skill flags instances idle beyond a threshold such as 72 unused hours and includes them in the escalation report.

Can I test AWS cost analysis without live credentials?

Yes. Set HERMES_LAB_MODE=mock to run the workflow against simulated data without real AWS calls. Switch to live mode with valid credentials and AWS_REGION configured for production analysis.

What environment variables does AWS cost anomaly detection need?

The Skill requires AWS_REGION, EC2_INSTANCE_ID, and HERMES_LAB_MODE as environment variables, plus AWS CLI v2 installed. Missing variables prevent the deterministic Cost Explorer and EC2 queries from running.

Will this Skill terminate or modify my EC2 instances?

No. The Skill is read-only by design and explicitly forbids aws ec2 terminate-instances and any modification of Reserved Instances. It only detects, reports, and escalates findings for human action.