Skip to Content
Use casesCloud cost report

A cloud cost digest that explains the change

See where the money went without opening a console. A deputy reads your cloud spend on a schedule and sends a digest: what changed since last time, the top movers, and anything that looks unusual.

How it works

  • Trigger. A weekly schedule, for example Monday at 07:00 in your time zone.
  • What the run does. It queries your spend data with a read-only credential, compares it with the previous period, and writes the digest.
  • Who is contacted. The deputy’s owner gets a heads-up with the digest, on Home and in Slack when your admin has connected Slack.
  • What you see. One short message with the totals, the biggest changes and links.

The deputy needs no special cost package. It uses the access you give it. That can be a read-only credential for your cloud CLI, a billing export in a database, or any data source with a read-only credential.

Set it up

  1. Create a read-only credential for the data source you want to report on, in your cloud account.
  2. Connect it in Marshal. For AWS, add the aws package and connect an Access key + secret. For Google Cloud, add the gcloud package and connect a service account, which also lets the agent run bq queries. See Credentials and connections.
  3. Create a manifest with the packages claude-code and the cloud package. The package allows its own hosts.
  4. Open Deputies, select New deputy, and fill in Name, Description, Manifest and Owner.
  5. In the deputy, select New mission. Paste the prompt below into Prompt, select Dry run, then Activate.
  6. Expand the mission. In the Triggers list, select Schedule.
  7. Set Repeats to weekly, On to Monday, At to 07:00, and pick your Timezone. Or select Advanced and enter 0 7 * * 1 in Cron expression.
  8. Select Create.

What you should see: the schedule in the trigger list with its next run time and an on badge.

Example mission prompt

Write the weekly cloud cost digest.

1. Using the read-only credential, get spend for the last 7 days and
   for the 7 days before that, grouped by service.
2. Report the total and the change in percent.
3. List the top 5 services by increase, with the amounts.
4. Flag anything unusual, such as a service that is new this week or a
   sudden jump in a single day.
5. Send me a heads-up with the totals and the top movers. Keep it
   under 15 lines.

Make it yours

  • Keep your budgets and team tags in the deputy’s Context, and last week’s totals in Memory.
  • Report daily with 0 7 * * *, or monthly with 0 7 1 * *.
  • Query a database of billing exports instead. Connect it read-only and say so in the prompt.
Weekly security checkIssue triage