# cost-change-investigation

> Claude/Codex skill by [@costory-io](https://omgskills.com/library/costory-io/index.md) · 2 stars · Updated 2026-10-21

Use when investigating a cost change to explain what changed, when, and the best-supported drivers with contribution, timing, usage, metric, event, alert, and terminology evidence. Call get\_skill with skillId "cost-change-investigation" before starting the investigation.

Tags: agent-skills, aws, azure, claude-code-plugin, claude-plugin, cloud-cost, cost-allocation, cost-optimization, cursor-plugin, finops, finops-agent, finops-mcp, gcp, gemini-cli-extension, kubernetes, llm-cost, mcp, mcp-server, model-context-protocol, remote-mcp

## Install

```sh
git clone https://github.com/costory-io/costory-finops-mcp-skills /tmp/costory-finops-mcp-skills && ln -s /tmp/costory-finops-mcp-skills/plugins/costory/skills/cost-change-investigation ~/.claude/skills/cost-change-investigation
```

## From README

Cost Change Investigation Role You are a senior FinOps lead explaining a cost change to stakeholders. Goal Explain what changed, when, and the best-supported driver(s). Produce a short client-facing summary and a developer-facing methodology. What The Client Sees The client sees the specific group-by label, numeric cost change, original cost, new cost, and the summary you generate. Example: AmazonAthena : +$2.66K, +8.29%, $32.05K → 34.71K | Costs increased because of .... Rules: Never mention numeric cost-change values already displayed for the client. You may mention cost or metrics for the specific factor(s) that explain the change, for example: Costs increased because of a 3x increase in Athena query . Spending increased by $2500 in "specific api type". Workflow Call MCP getcontext first. Use query, search, listevents, listalerts, listmetrics, and suggestusagemetrics only when they add context, validate a driver, explain timing, or connect cost to .

## Links

- HTML page: https://omgskills.com/library/costory-io/costory-finops-mcp-skills/plugins/costory/skills/cost-change-investigation/
- GitHub: https://github.com/costory-io/costory-finops-mcp-skills
- Author: [@costory-io](https://omgskills.com/library/costory-io/index.md)

## More from this repo

- [bigquery](https://omgskills.com/library/costory-io/costory-finops-mcp-skills/plugins/costory/skills/bigquery/index.md) — Used when the user asks about BigQuery costs, SKUs, on-demand Analysis vs capacity slots/editions, leftover on-demand,...
   - [@costory-io](https://omgskills.com/library/costory-io/index.md) · 2 stars
- [dashboards](https://omgskills.com/library/costory-io/costory-finops-mcp-skills/plugins/costory/skills/dashboards/index.md) — Used when creating or extending Costory dashboards, generating interesting FinOps overviews (suggest\_groupby +...
   - [@costory-io](https://omgskills.com/library/costory-io/index.md) · 2 stars
- [recipes](https://omgskills.com/library/costory-io/costory-finops-mcp-skills/plugins/costory/skills/recipes/index.md) — Used when a user states a FinOps \*outcome\* rather than a tool.
   - [@costory-io](https://omgskills.com/library/costory-io/index.md) · 2 stars