Cost context in Terraform pull requests
Add current cost context for the resources touched by a Terraform pull request.
Runs in
Claude Code · GitHub
First optimization recommendation
The next day
ROI
Pays for itself with the first recommendation you act on
Claude Code
>
This PR changes the instance type of the search cluster. What does that cluster cost today?
⎿
… +24 lines (ctrl+o to expand)
⎿
… +16 lines (ctrl+o to expand)
●
The search cluster costs €9,300/month today (prod). Owner: Search team.
>
Try "write a test for main.py"
? for shortcuts
You decide
Reviewers decide with cost in view.
Playbook
What the agent does
From what Costory notices to what you decide. Costory suggests the next step in conversation, and you decide whether to go ahead.
Costory notices
A Terraform PR touches existing resources.
Costory investigates
01
Detect resources
From the PR diff.
02
Current cost
Query Costory.
03
Comment
Post context on the PR.
Where you see it
Claude Code
You decide
Reviewers decide with cost in view.
Why it matters
Infrastructure changes are reviewed without knowing what the affected resources cost today.
Who it’s for
Platform engineers
Where it runs
Claude Code · GitHub
What you get
What lands in front of your team
Informed reviews
Cost next to the diff.
Owner context
Who owns the resource.
History
Recent changes.
Sources and assistants
What it connects
Data sources
Example prompts
Or drive it yourself
Review
This PR changes the instance type of the search cluster. What does that cluster cost today?
FAQ
Questions about this playbook
Which agents and assistants work with Costory?
Claude, Claude Code, Cursor, VS Code with GitHub Copilot and Dust connect to the hosted Costory MCP server with OAuth.
How long does this playbook take to set up?
Connecting your billing data and the Costory MCP takes under 30 minutes with Terraform or CloudFormation. The playbook itself takes minutes: pick the scope, the trigger and the Slack channel. The first billing data lands the next day, and the agent starts from there.
Can we adjust what the agent does?
Yes. You choose the trigger, the scope (team, service, environment), the channel and the format, and you can pause or change it at any time.
Does Costory change anything in our cloud accounts?
No. Costory reads billing exports and the metrics you connect, and has no write access to your cloud. Actions it takes create Costory objects only: alerts, reports, dashboards and events. Your team stays in control of every change.
Step-by-step guide in the Costory docs
Related playbooks
Run these alongside it
Costory notices
A deploy is followed by a cost change on the same service.
Cost impact of every deploy, from GitHub events
Capture deploys, PR merges and releases from GitHub or your CI/CD pipeline, and see which ones changed cost.
See the playbook
Costory notices
Monthly, or when a team's AI coding spend jumps.
Cursor and Claude Code spend per developer
Track AI coding tool spend per user and per model, from Cursor and the Anthropic Claude Code connector, next to the rest of your cloud.
See the playbook
Costory notices
A developer is about to change a service.
Cost context in your terminal with Claude Code
Connect the Costory MCP to Claude Code so the agent checks what a service costs, how it changed and who owns it before you ship a change.
See the playbook
Put this playbook on call
Included in every plan, from €250/month. 30-day free trial: connect in under 30 minutes, get your first optimization recommendation the next day.
First optimization recommendation
The next day
ROI
Pays for itself with the first recommendation you act on
Setup
About 30 minutes
Data residency
EU
Access
Read-only on your cloud