When should you use it?
- You do daily market prep from many sources
- Your scrapers keep breaking
- You want ideas challenged before you act
Not for: Automated order placement; Investment advice for other people
What do you need, and what do you get?
You need
- Watchlist and sources
- A map file listing each agent's job
- A contract file with what each agent may and may not do
You get
- Daily prep notes per agent
- Red-team verdicts with reasons
- A short list of ideas that passed
How does it work, step by step?
- Write the mapList each agent, its one job and who it reports to.
- Write the contractSpell out allowed tools, sources and the rule that no agent can place a trade.
- Add the red teamGive one agent the job of attacking every idea and returning Pass or Fail with reasons.
- Run the morningLet research agents prepare notes and send candidates to the red team.
- Decide yourselfRead the passed ideas and their objections, then make any trade by hand.
The prompt
Our own prompt, inspired by u/Glad-Ranger1879 on r/GrokBot and written to work in Grok Bot. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
You are the Red Team agent. For each trade idea below, try to break it. Check the thesis, the timing, upcoming events and what would make it wrong.
Ideas: {ideas}
Return PASS or FAIL for each with the three strongest objections and the data behind them. You cannot place trades or suggest position sizes.Inspired by u/Glad-Ranger1879 on r/GrokBot: Running an 11-agent team on Grok Bot for my trading prep: what works and what doesn't. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Agents can share the same blind spot; give the red team different sources.
- Scraped prices can be stale; check quotes in your broker before acting.
- A pass is not a recommendation; you still own the decision.
Our take
Most multi-agent research setups produce more material; the clever part of this one is an agent whose only job is to find reasons not to trade, and a rule that nothing proceeds until it passes. That adds friction exactly where overconfident research does damage. The second rule matters even more: no agent can place a trade, so the whole system stays a preparation desk that informs a human decision. The two scoping files per agent are a cheap way to prevent overlap, since each agent knows its own job and what it must deliver. To keep the red team useful, give it inputs the other agents do not use, such as bearish write-ups or risk data, otherwise it simply agrees with them. Review what it rejected each week and whether those calls were right, which tells you if it is catching real problems or just slowing things down. Treat everything the agents produce as research, check prices against your broker before acting, and keep position sizing a decision you make yourself.
Where the time goes back: Morning prep arrives sorted and already challenged, so your time goes to deciding.
FAQ
Why separate files?
Can models be pinned per agent?
Source and credit
Inspired by u/Glad-Ranger1879 on r/GrokBot. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Running an 11-agent team on Grok Bot for my trading prep: what works and what doesn't
- Creator
- u/Glad-Ranger1879 on r/GrokBot
- Published on
- Original date
- Oct 6, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Grok Bot
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends, bookings or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.