grok-bot-usage：给 Grok Bot 装用量表

Solomon Rojie @Solomonrojie原推发布于 2026.10.25

在 X 上打开原推

THIS IS AN ACTUAL F*CKING CHEAT CODE you can put a usage meter on your Grok Bot setup and see how much allowance is left before another routine eats through it the open-source grok-bot-usage shows weekly usage, reset dates, and on-demand spending across your connected accounts the idea: let code read the meter, record what changes, and bring Grok Bot in when there’s something worth investigating you start with one command: gbu here’s the split: → weekly usage shows how much of your allowance is consumed → reset dates show how long the remaining budget needs to last → on-demand spending shows the extra bill building up → JSON output lets scripts keep a record without asking a model to read the dashboard three moments worth measuring: → before a recurring workflow starts → after its result is ready → after you change its instructions, schedule, or handoff the meter reports account-level usage. compare workflows in isolated test windows so another bot’s background activity doesn’t get credited to the job you’re measuring code collects the numbers. Grok Bot investigates the expensive patterns. you decide what stays want the allowance visible while you work? QuotaRail adds a macOS usage rail with Grok Bot weekly usage build the monitoring workflow like this: → read gbu --json at the start and end of a test → save timestamped readings in USAGE_LOG.jsonl → record the task, outcome, and whether you accepted the result → mark overlapping activity instead of inventing precise attribution → compare the original workflow with one focused change → report missing data as unknown → keep routine data collection in scripts paste this into Grok Bot ↓ “Build a usage-monitoring workflow around grok-bot-usage: 01 / Review the repository and show me the installation steps. Let me complete account sign-in in the browser. 02 / Confirm which usage fields are available. Never estimate missing token counts or spending. 03 / Create a local log for timestamped readings, task names, accepted results, and overlapping activity. 04 / Run one controlled comparison on a recurring job. Change one thing and compare usage alongside output quality. 05 / Show the findings before proposing any changes to my bots or routines.” set it once. your next session is cheaper and safer before you type a word. the article below explains 7 changes you can test against those readings, from smaller working context to reusable research and bounded retries ↓

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