All use cases

Engineering

Tip only: schedule routines, do not poll every few minutes

1 / 5 / 30 minute routines chew Grok Bot usage before the day starts.

Share

What hurt

Keegs (@Bobby_1509) told someone burning Heavy-plan Bot usage in four hours: if a routine runs every 1, 5, or 30 minutes, it will chew usage fast. Prefer a scheduled routine once or twice a day instead. Tip only.

What to install or create

Audit routines. Delete or rewrite anything on a sub-hourly loop into a coarse daily or twice-daily cron. Pairs with the Cursor model-default tip.

Bots

  • No new bot. Follow the first-run steps.

Plugins

  • None on day one. Follow the first-run steps.

Files

  • A list of your current routine schedules.

Routines

  • Prefer once or twice daily. Avoid every 1 / 5 / 30 minutes unless truly incident-critical.

The prompt

This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.

First run

  1. 1Read https://x.com/Bobby_1509/status/2095677873889964074. Tip only.
  2. 2Open your Grok Bot routines list.
  3. 3Anything on a 1 / 5 / 30 minute loop: pause it or rewrite to once/twice daily.
  4. 4Optional: also pin cheaper Cursor task + cloud default models (see cut-cursor-model-defaults).

Approval fence

No send, post, or spend. Editing schedules only.

What to tweak

Steal the cadence rule. Frequency is a budget setting.

Source

Keegs @Bobby_1509 · Original post

Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.

Browse templates

Browse team blueprints

Pro pack

Want the full setup, not just the idea?

Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.

See Pro