Build a monthly usage audit page that labels every routine

How this helps you

You see which routines are worth their usage and get exact changes to make, on one page you refresh monthly.

✦ Try it

Here are screenshots of my usage page and billing page: [screenshots]. Audit how my Bots use my weekly usage and build the results as a page called [Usage audit]. List every routine with its Bot, schedule and runs per week, and label each one Keep, Slow down, Change check or Retire, with a reason. For Change check, write the exact check-first line to add. Add a section for other drains: long chats, old group chats, browser jobs, third-party models, images and video. Mark which numbers are verified and which are estimated. Don't change, pause or delete anything until I approve.

Fill in: [screenshots]: the usage and billing pages. [Usage audit]: any page name you like.

What they did

The usage page shows one number for the whole account, with no per-Bot or per-routine breakdown yet (Kacper says the team is working on it), and your Bot can't look up your usage. So Kacper Rutkiewicz gave his Chief of Staff Bot two screenshots, his usage page and his billing page, and asked it to audit how his Bots use his weekly usage and build the result as a page called usage audit. He credits Michael Fenech's routine audit prompt on X as the inspiration. The page listed what ran this week, routine runs per week, what to do first, and every routine with one of four labels: Keep, Slow down, Change check (add a check-first line) or Retire. An 'other drains' section found a very long chat history on one Bot and two old group chats he couldn't see in his sidebar. It also separated verified amounts from estimated ones.

Who it's for: People with several Bots and routines whose weekly usage runs out early.

Before you start

A few Bots with routines that have run for at least a week.
Screenshots of your usage page and billing page.

How to try it

Take screenshots of your usage page and billing page and send them to your main or Chief of Staff Bot with the prompt below.
Read the routine table first. Slow down routines that run more than the job needs: a 15-minute schedule is 672 runs a week, weekdays at 8:00 AM is 5.
For Change check routines, add a check-first line at the top: compare one small thing to last time and stop if nothing changed. Kacper calls this a user tip, not an official one.
Retire what you don't use. Pause or delete it; hiding a Bot doesn't pause its routines.
Ask the Bot to make it a routine that rebuilds the page on the 1st of each month. Pages don't refresh when you open them; the routine rewrites it.

What to expect

A page with a 'do these first' list, a table of routines each tagged Keep, Slow down, Change check or Retire, ready-to-paste check lines, and an other-drains section.

Common mistakes

Running the audit weekly or daily. It uses usage too; monthly is enough.
Expecting instant results. Kacper says the difference shows over the next week.
Leaving helper steps on Claude or GPT. Third-party models bill paid credit at API pricing from the first use, even while your weekly meter has room.
Approving every change at once without reading the reasons.

Related tips

Analyse your own usage CSV: Export usage from the Usage page and ask your Chief of Staff Bot how to cut it.
Make routines cheaper: events, slow schedules, change checks: A 5-minute routine wakes 8,640 times a month. Use an event trigger, the slowest schedule that works, and a cheap change check.
How Pages stay up to date (and what they cannot do): Pages are not live: a routine rewrites them. Know the limits before you build many.
Out of usage? Run these five checks before you buy credits: Grok Bot says you're out of usage but you still have credit? Check the weekly pool, the monthly cap, the meter, the account, then what's eating it.
Five no-small-talk rules for Bots that talk to each other: Paste five rules into each Bot so group chats and handoffs stop filling up with 'got it' and thumbs-up replies.
A read-only usage audit across your whole Bot team: One prompt has your chief of staff check every Bot's routines, schedules and triggers, then report what to pause, slow, narrow or merge, and change nothing until you approve.