Performance playbook

Cloud Cost Anomaly

Weekly billing anomaly detection correlated against infrastructure changes and deploys to name the change most likely causing a spike.

Once a week, pulls cloud billing broken down by service and SKU, detects anomalies against a trailing baseline, and correlates each spike against infrastructure changes and deploys in the same window. Files a ticket naming the change that most likely caused each regression.

Identifier: cloud-cost-anomaly
Version: 1.0.1
Steps: 5
Triggers: 1

cloud
cost
anomaly
billing
infrastructure
weekly

When it runs

Scheduleschedule.weekly

Schedule: Every Monday at 07:00 UTC 0 7 * * 1
Timezone: UTC

The pipeline

The graph below is the one the workflow opens with in the builder, same steps, same layout, drawn on the same canvas. The run playing through it is a simulation; the branches and conditions are real.

Trigger

Weekly Schedule (Monday 07:00 UTC)

The event that starts the run.

HTTP Request

Fetch Billing Data ⚠️ SET YOUR BILLING ACCOUNT

Calls an external HTTP endpoint with vault-resolvable headers.

Clone

Clone Infrastructure Repository ⚠️ SET YOUR REPO

Shallow-clones the repository at the right ref.

Agent Run

Analyse Cloud Cost Anomalies

One agent works the task with its toolkit.

Create Ticket

File Cost Anomaly Ticket

Opens a ticket on the connected tracker.

React Flow

01
Weekly Schedule (Monday 07:00 UTC)trigger
The event that starts the run.
02
Fetch Billing Data ⚠️ SET YOUR BILLING ACCOUNThttp.request
Calls an external HTTP endpoint with vault-resolvable headers.
03
Clone Infrastructure Repository ⚠️ SET YOUR REPOgit.clone
Shallow-clones the repository at the right ref.
04
Analyse Cloud Cost Anomaliesagent.run
One agent works the task with its toolkit.
05
File Cost Anomaly Ticketticket.create
Opens a ticket on the connected tracker.

The agent

Cloud Cost Analyst

Base type: Senior Developer
Temperature: 0.2
Max iterations: 40
Tools: 7

Memory · 2

memory_writeWrite Memory · write
memory_readRead Memory · read

Terminal · 1

run_terminal_cmdRun Terminal Command · write

Filesystem · 1

read_fileRead File · read

Code search · 1

code_searchCode Search · read

Tickets · 1

create_ticketCreate Ticket · write

Status · 1

update_statusUpdate Status · write

Related playbooks

Bundle Size GuardBuilds the PR branch and base branch, compares bundle sizes, and attributes growth to specific imports or missing dynamic imports.LLM Cost Regression WatchWeekly comparison of execution cost against the trailing baseline, flagging agents whose cost-per-run rose and attributing the cause.N+1 DetectorFinds database or network calls executed inside iteration and proposes a batch fetch, join, or safe concurrency rewrite.

Import this playbook Back to the catalogue