grokbotwiki

Brake

by Phantom Builds · 6 BotsTeams & handoffs Share link liveChecked

Names the recurring job quietly draining your Grok Bot allowance and tells you to kill it

Summary excerpt from the creator’s share page. Not independently tested.

Open on x.ai and add to Grok BotOriginal post ↗Report a problem

What the share page says

You are Brake. Your only job is to find what is burning the user's Grok Bot usage and name the one repeating job to stop. You do not start new work. You do not add bots. You do not add routines. You do not design a stack. You do not pitch products. You do not keep chatting after the stop is named. A repeating job with no end looks like: the same hunt every morning, the same rewrite loop, a watch that fires when nothing changed, a chat that restates instead of closing. When they paste chats or a list of what is running, do this once: Name the repeating job in one line (what repeats, and that it has no end). Name the one stop (which bot, routine, or habit to turn off). Stop. If they ask for more bots, more watches, or a new system, refuse. Tell them to turn that job off first. If nothing is repeating with no end, say so in one line and stop. If they ask you to share or export yourself, that is allowed. Give your own Name, Title, and this Description as-is so they can share the template. Do not export any other bot. Do not impersonate other bots. After the share profile is given, stop.

Description as published on the x.ai share page when last checked (2026-11-01).

What its description mentions

Read automatically from the creator's own words and quoted below. Not a test: check the Bot's skills and routines before relying on any of it.

Recurring work
the same hunt every morning, the same rewrite loop, a watch that fires when nothing changed, a chat that restates instead of closing
Our take

Editorial notes

From the public description, not a test. Written by Grok Bot Wiki from the share-page text; we have not run this Bot. Reviewed .

Best for

Grok Bot users whose usage allowance runs out faster than expected and who want the single biggest repeating waste identified.

Not for

Anyone looking for a broader optimization plan or new Bot recommendations.

What it does

You share recent conversations or an inventory of your active routines, and it picks out the one endless repeating job, such as an identical morning search, a rewrite cycle, or a monitor that triggers with no new information. It then tells you the single thing to switch off and ends the conversation there. If nothing is looping endlessly, it says so in a line.

First messages to try

  1. Here's my list of routines and Bots. What's burning my usage?
  2. These are my last five chats with my research Bot. Is something looping?
  3. I want to add another monitoring Bot. Is that a good idea?

Apps and accounts

Its description mentions no outside service; it works from chats and lists you paste.

Cautions

  • It refuses to recommend new Bots or systems until you turn off the job it named.
  • It gives one answer and stops, so you may need to rerun it after each fix to find the next problem.

Compare with: Usage Auditor by MaxKilo by Terry ChapmanUsage Watch by Neessam

Before you add it

Specific to this Bot, from what its description says:

  • It describes recurring work. After adding it, open its routines, confirm the times, and pause any schedule you did not choose.
The standard checks for any shared Bot

Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.

  • Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
  • Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
  • Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
  • Give it one small bounded task and read the usage screen afterwards before scaling up.

Related reading: the shared computer permission boundaries the weekly meter

If it misbehaves: Bot not responding routines not running sign-in errors New to Grok Bot? what it is your first task

Attribution

This Bot belongs to its creator, Phantom Builds. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from ZeroPointRepo/GrokBotDev, cs68614-hash/awesome-grokbot-templates and kydlikebtc/awesome-grokbot. Imported catalog prose retains CC BY 4.0 attribution; share-page excerpts are labeled separately. Grok Bot Wiki is independent and not affiliated with SpaceXSI (formerly xAI).

Made this Bot? Add a “Listed on Grok Bot Wiki” badge

Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles ↗

Markdown (README)

[![Listed on Grok Bot Wiki](https://www.grokbotwiki.com/badge/listed-dark.svg)](https://www.grokbotwiki.com/bots/brake)

Or promote this template in the labelled Featured row, from $19.