Menu
Query current AWS billing data and identify top cost drivers using Cost Explorer.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Conduct a decision-tree interview with the user to lock in requirements, motivation, scope, and non-goals before planning.
Stage 3 of three-stage planning pipeline. Produce a file-level implementation plan via detail-planner/detail-reviewer loop, then get user approval. Inputs are confirmed intent (<session-id>-intent.md) and outline (<session-id>-outline.md) from prior stages.
Edit source code for the current task. Delegates editing and lint/typecheck/self-repair to a subagent.
Plan and write test cases with high reasoning effort. Test iteration runs in a subagent to minimize confirmations.
Explore the codebase to understand existing patterns, constraints, and relevant files before planning.
Investigate git history, docs/history.md, and GitHub issue/PR timeline since the relevant issue opened, to surface changes that may invalidate the issue's premises.
| name | aws-scan-cost |
| description | Query current AWS billing data and identify top cost drivers using Cost Explorer. |
| model | sonnet |
| effort | medium |
| context | fork |
ASC-1. Verify prerequisites. Requires ce:GetCostAndUsage.
ASC-2. Query (pass --profile $AWS_PROFILE; Cost Explorer ignores region):
aws ce get-cost-and-usage --time-period Start=<YYYY-MM-01>,End=<today> --granularity MONTHLY --metrics BlendedCost --group-by Type=DIMENSION,Key=SERVICE$AWS_STATE_DIR/cost-<YYYYMMDD>.json.
ASC-5. Write human-readable summary to $AWS_STATE_DIR/cost-<YYYYMMDD>.md:Skip if $AWS_STATE_DIR/cost-<YYYYMMDD>.json exists and is less than 4 hours old.