devops-agent-cost-insights

Overview

This skill provides the methodology for gathering and calculating AWS DevOps Agent cost data. It intentionally does NOT prescribe a fixed output format. The consuming agent (chat, custom agent, etc.) decides its own presentation (plain text, multi-space tables, single-space visual dashboard with charts, etc.) based on its own prompt/output spec. Follow the steps below to gather and compute correct numbers; format them however the calling context requires.

Execution visibility

The consuming agent's output contract controls visibility. When it requires silent, final-only execution:

• Perform skill/reference reads, planning, tool calls, pagination, distillation, calculations, retries, and Step 7 validation without assistant-authored progress messages.
• Keep checklist state, intermediate values, query IDs, raw records, arithmetic, and rejected records internal.
• Do not announce file reads or tool calls, react to results, or narrate what happens next.
• Return only the consuming agent's single final response after its artifact operation. A compact validation result table is allowed only when its final template explicitly requires one.

This skill must add exactly $0.00 to the bill. Never StartQuery, StartQueryExecution, or GetMetricData — and never any other operation the zero-cost rule names below. Each is a paid API, so issuing one bills the account this report is about. If a figure is only reachable through a paid call, it is unavailable; say so. This is the zero-cost rule, restated at Step 1 and attested in Step 7.

"Read-only" is not the safety test. GetMetricData reads only your own metrics and is billed per metric anyway. Before using any call not already named in the steps below, classify it per Operation classification in Step 3; an operation you cannot confirm as free is unclassified, not free.

Four things to cover every time:

1. Discovery: enumerate Agent Space(s) and DevOps Agent role(s) in scope (may be one space or all spaces in the account, depending on what's requested)
2. Direct usage: agent-seconds billed (investigations, evaluations, chat), per space
3. Downstream: AWS API costs from agent-initiated calls (Logs Insights, Athena, X-Ray, CloudWatch), attributed via CloudTrail, traceable by query ID / query execution ID
4. Grouping: if multiple spaces/roles are in scope, group cost by Agent Space ID and by DevOps Agent Role ARN; if scoped to a single space/role, a single summary suffices