Grok Bot Usage Saver: inventory routines, read the meter, propose calmer schedules (unofficial guide)

The short answer

Open Usage first. On The X Subscription that's Usage at grok.com/dashboard (or Settings → Usage in the Grok app). Note percent used, next reset, and the per-product breakdown.

Ask your Bot to list every routine across every Bot: schedule or trigger, what each run reads, active or paused. Flag hourly jobs, Slack "any message" triggers, overlapping inbox reads, and routines you never open.

Have it propose at most three calmer changes with trade-offs. You Allow each change by number. The free Usage Saver skill encodes that loop.

This guide is independent and unofficial. It isn't affiliated with or endorsed by xAI, Grok, X, or Cursor.

Why this page exists

r/GrokBot threads through October 2026 keep asking the same thing: usage gone by mid-week, setup week burned the pool, group chats felt expensive, top-ups bought less than expected. Official docs already warn that hourly routines and busy Slack triggers can spend a week in a day (Cursor routines help).

The Usage Saver skill does not restore allowance, explain sudden meter jumps, or prove a glitch. It helps you see your own schedule.

Step 1: inventory before you upgrade

For each routine, record: Bot name, routine name, schedule or trigger in your words, Active or Paused, what it reads, and whether you actually use the output.

Common waste patterns from user reports and docs: the same inbox on two Bots; hourly checks when daily would do; weekend runs nobody reads; Test runs left on large inputs; every Bot answering an untagged group message.

Prefer connectors over browser automation when a connector exists. Browsing is usually heavier.

Step 2: three proposals, then stop

Ask for at most three changes, largest savings first. Each one should say what changes, why it should use less, and what you give up (fresher results, overnight alerts).

Good defaults: daily or twice-daily instead of hourly; weekday waking hours instead of 24/7; narrow Slack/GitHub/email triggers; merge overlapping routines; pause unused ones.

Change nothing until you say Allow #1, #2, and/or #3. Then change only those items and confirm how to undo (Resume / Edit back).

Step 3: recheck once, don't meter-watch

After approved changes land, recheck Usage after a day or two. Do not create a short-interval routine whose only job is to recheck usage — each check uses usage too.

If you still blow the pool most weeks after a calm schedule, compare top-ups with the next plan at x.ai/pricing, or read the Heavy vs Ultra and "should I switch away" guides.