DEVOPS
Comment projected cost impact on PRs that touch cost-sensitive infra
When a pull request changes infrastructure code, this agent estimates the recurring cost delta of the change using recent spend history and posts a plain-English projection…
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub pull request opened or updatedGitHub
- LogicFilter to PRs touching cost-sensitive infra files
- ActionFetch service recent spend trend from DatadogDatadog
- LogicEstimate recurring cost delta from diff and trend
- OutputPost projected cost-impact PR review commentGitHub
What it does
Shifts cost attribution left to review time. When a PR touches infrastructure definitions, the agent reads the diff, looks up the affected service's recent spend trend, reasons about whether the change likely raises or lowers recurring cost, and leaves a review comment with a projected monthly delta and the assumptions behind it.
When to use it
Use it when cost surprises keep landing in production and you want reviewers warned at the PR stage. Best for teams whose infra lives in version-controlled config and who already track per-service spend.
How it works
- 1A GitHub pull-request event triggers the workflow when infra paths change.
- 2A logic step filters to PRs touching cost-sensitive files; others are skipped.
- 3The agent fetches the changed service's recent spend trend from Datadog.
- 4It reasons over the diff and the trend to estimate a recurring monthly cost delta with stated assumptions.
- 5It posts the projection as a PR review comment, flagging large increases for extra scrutiny.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect DatadogMetrics, traces, log search.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.