Grok Bot team reviews three token leaks from live routines
The Grok Bot team livestreamed three token-wasting cases, including one prompt that made the bot read every open ticket, and shared fixes like event triggers and passing ticket IDs.
one prompt, "reply to alex", made a grok bot read every open ticket a ticket id would have done the job. that's 1 of 3 token leaks the grok bot team hit on stream the other two: → a routine set to every 15 minutes fires about 100 times a day, and every run burns tokens → an agent slept 300 seconds waiting on a 1-minute test several people on the team ran 15-minute routines because the task felt urgent. it wasn't the fixes they landed on: → an event trigger instead of a schedule → reports once or twice a day → pass the ticket id → say nothing when nothing changed on the support session a medium ticket cost about $1 to $2. simple billing tickets fell to about $0.20 once a script handled them the 5 routines the team ran on stream, all silent when nothing changed: → 8:30 morning brief: calendar, overdue, waiting on you → 9:00 and 13:00 promise keeper: open asks past their date, nudges drafted, never sent → before each call: who's on it, what changed, one suggestion → when a call ends: promises listed, replies drafted in your voice → 3:00 nightly audit: small PRs for the morning, each with proof, never merged the catch: read those dollar figures as order of magnitude, they come from one session a bot that reports every 15 minutes teaches you to ignore it every hour your routine runs for nothing, you pay for a message you'll never read bookmark this and fix your schedule tonight, the no-leak routine prompt is in the article below ↓
This post quotes another post: “Grok Bot setup guide: build the whole workflow with one message”