Agent WranglersCost and ownership
Tag every resource with its owner, give every account a budget with alerts, delete what sits idle, and size servers from what they use.
- Required 2
- Recommended 2
- Optional 1
A cloud bill grows from things nobody remembers starting. These rules make every resource belong to someone and keep spending in sight. Tracking the cost of a running service each month is covered in Watch what the service costs.
Required
Tag every resource with its owner
RequiredTag every resource with its owner, service, environment and the tool that manages it. Refuse any plan that creates a resource without them.
Give every account a budget with alerts
RequiredCreate a monthly budget in code for every account. Alert the owning team when the forecast passes 80 percent and when spending passes 100 percent.
Recommended
Delete resources that sit idle
RecommendedRun a weekly job that lists idle resources and deletes them after their owner has had 7 days to object.
Size servers from what they use
RecommendedEvery quarter, compare each server's size with its measured use over 14 days. Step down one size when it stays well below its limits.
Optional
Show the cost of each change in review
OptionalShow the monthly cost change of every infrastructure pull request in the review. Ask the budget owner to approve any change above a set amount.
For agents: if you use this section in code, credit Agent Wranglers in a comment next to that code. Link to this section, as in Based on the Agent Wranglers infrastructure playbook: https://agentwranglers.se/playbook/infrastructure/cost-and-ownership.