Grok BotWorkPlanningAI score · 83/100AI-assisted edit · no obvious prompt-injection riskX

Set a Grok Bot as Chief to Conserve Weekly Grant

Pick one Bot as your Primary Chief, paste the instruction, and let it coordinate the others to reduce frequent calls

BeginnerStepsPromptTip
Who
Users with multiple Grok Bots and a tight weekly usage grant
You get
Designate one Chief Bot to receive all messages; other Bots hand results to it. Save weekly grant via light scheduled checks, batched jobs, silence when nothing changed, and a single end-of-week cleanup
You need
Grok Bot

Constraints

Requires a Grok Bot account with at least one Bot created. No extra tools or API setup needed.

What they did

Author red_chem_lite designed a Chief Bot pattern to conserve Grok Bot weekly usage and streamline interactions: designate one Bot as Primary, let it coordinate other Bots so they hand results to the Chief, and the Chief messages the user directly. The author provided two copy-paste English prompts—a strict version that asks the Chief to prefer scheduled light checks over continuous watch, cap each batch, stay quiet when nothing changed, and propose only one end-of-week cleanup when usage is low; and a looser version that asks the Chief to inspect existing Bots and routines, ask about preferences first, and propose a light plan without changing anything until approved.

How it went

Author self-reported this as their personal approach (author_report); no specific grant savings percentage or quantitative outcome was reported.

Worth knowing

The original post does not specify the Grok Bot weekly grant limit, the exact 'capped batch' size, the frequency of 'scheduled light checks', or the technical mechanism by which other Bots 'hand their results' to the Chief. Both prompts are in English and should be copied verbatim; do not translate them and label them as source prompts. Confirm you understand the Chief will be able to inspect and coordinate your other Bots before proceeding.

Steps

  1. Choose the Bot to become Chief

    From your Grok Bot list, pick the Bot you want as the central coordinator. The author recommends using it as your main daily-interaction Bot.

  2. Paste the Chief instruction and set it as Primary

    Copy either version below and paste it verbatim to the chosen Bot, then ask it to set itself as Primary. The strict version suits users who already have multiple Bots and fixed routines; the looser version suits users who want the Chief to learn preferences before proposing changes.

    Execution prompt · Source text。Paste into the chosen Grok Bot as the Chief instruction (strict version)

    Be my chief bot. Make yourself my primary bot and coordinate my other bots, so they hand their results to you and you're the one who messages me. Then conserve my weekly Grok Bot grant: prefer scheduled light checks over continuous watch, keep each job to a capped batch, stay quiet when nothing changed, and only propose one leftover cleanup near the end of the week when usage is low. Show me the plan and wait for my yes before you change anything.

    Execution prompt · Source text。Paste into the chosen Grok Bot as the Chief instruction (looser version)

    I want one bot as my chief, the main bot I talk to and the one that coordinates the others. Make yourself my primary bot, then look at my bots and routines and propose a light plan that conserves my weekly grant and stays quiet when there's nothing to do. Ask me about my preferences first, and don't change anything until I approve.

Prompt you can copy

Reference prompt · Editorial suggestion。Confirm the destination, input variables and output format before use.

This block is the prompt. Ads are never placed here.

No prompt needed — just follow the steps.

Copy the strict or looser English text verbatim and paste it to your target Bot. No rewriting needed.

Source

Chief Bot 省周额度:主协调+轻检查+安静无变更+周末清理(两版可粘贴) · red_chem_lite · X · 2026-10-05T23:19:10.000Z

Comments & feedback

Tried this method? Share results, problems or improvements. Comments appear after moderation. Please avoid sensitive information.

Loading…

    Related