Grok Bot 省 token 的 Checker/Runner/Scribe 提示词

fleyta @fleyta88原推发布于 2026.10.20

在 X 上打开原推

GROK BOT CAN WAKE UP 8,640 TIMES AND STILL GET ABSOLUTELY NOTHING DONE someone built a 14-part prompt that tackles one of the dumbest problems in AI automation. your bot keeps checking the same things, reading the same data and spending tokens on work that never needed to happen. in the cost model behind this setup: → full runs every 5 minutes: $397/month → cheap checks with selective execution: $45/month → 89% lower estimated spending not a subscription discount. just a different way to run the system. here's how the prompt reorganizes everything: → CHECKER looks for meaningful changes before expensive work begins → RUNNER handles the actual task when there's something new → SCRIBE records executions, skipped checks and failures the expensive model doesn't need to inspect every empty inbox or unchanged page. three rules make the difference: → separate monitoring from execution → never repeat work on identical inputs → keep sensitive actions behind human approval the overnight part is worth stealing too. from 23:00 to 08:00, the proposed workflow keeps risky operations in draft mode instead of leaving an approval request waiting for someone who's asleep. at 08:30, you get a morning report. every Monday at 09:00, the audit reviews failed runs, unnecessary checks and estimated spending. one system. clear responsibilities. an actual record of what happened. the execution path looks like this: trigger → cheap check → decision → runner → log → audit paste this into Grok Bot ↓ "Rebuild my routines around a change-first execution system. 1. Create three responsibilities: Checker, Runner and Scribe. Each must have a defined input, output and stopping condition. 2. Inspect existing schedules and replace unnecessary polling with event triggers where supported. 3. Before each expensive execution, compare the current source state against the last successful check. Skip unchanged inputs. 4. Configure an overnight rule from 23:00 to 08:00. Continue permitted low-risk tasks, but save actions requiring approval as drafts. 5. Produce a morning briefing at 08:30 covering completed work, failures and pending decisions. 6. Schedule a Monday 09:00 audit showing execution counts, wasted calls, estimated costs and recommended changes. 7. Test the workflow on safe copies before enabling any live automation. Show the full configuration, estimated usage and permission boundaries. Don't activate anything without my approval." the $397 and $45 figures are illustrative API-cost calculations, not measured Grok Bot bills. a bot that runs all night is easy to build. one that knows exactly when it has no business running is far more useful. read the engineering guide ↓ ↳ https://x.ai/bot/guides/grok-bot-for-engineering

这条是引用着另一条写的：x.com/gippp69/status/2109235458383216811