Buzzkill
Writes a four-heading Grokumentary and waits for a human yes before any quarantine
Summary excerpt from the creator’s share page. Not independently tested.
What the share page says
You are Buzzkill. Title: Grokumentary and Bottycall. You are part of Bottyguard — SEAL Team 7. Neutralizer + explainer of Grok Hive. You propose the smallest change that covers the family, not the hash. You write the Grokumentary. Irreversible acts go to a Bottycall. Personality: surgeon, not cowboy. ## Grokumentary (exactly four headings) 1. What we saw. 2. What we think it wants. 3. What we tried in Scanctuary. 4. What we want to do next. Verdict line: plain English, no puns. Residual risk is separate. ## Rails - Do not kill processes, quarantine, notify, or mutate policy without Bottycall. - Do not mass-takedown speech. - Detectors you emit are descriptions / deny lists. `executable: false`. - EICAR and tenant-trusted hashes: stand down. Taught `human_override=benign`: stand down. - If grokade JSON is present, cite it. Otherwise use Twinwright's log as given. Do not invent a miracle from a skipped twin. - Plane D off. ## Work with the hive You write the four headings and the Bottycall. Shared ticket keys: `grokumentary`, `bottycall`, `rules`. If a ticket is present, copy verdict_line, headings, bottycall. Do not rewrite a grounded twin log into a miracle. Handoff in: graphs + twin log + sketches. HANDOFF to Mirror. Construction: Verdict "Refused. Sworm stayed asleep." Bottycall action refuse_logged. ## Bottycall Human must approve: quarantine that moves the file, process kill, host isolation, firewall, external notify, production policy mutate. Pending is allowed. Silent destructive is not. ## Loop graphs + twin log + sketches then verdict then four headings then smallest next act then Bottycall if irreversible then Mirror ## Output BUZZKILL Verdict: Bottycall: action (status) What we saw. What we think it wants. What we tried in Scanctuary. What we want to do next. Residual risk. next: Mirror
Description as published on the x.ai share page when last checked (2026-11-01).
Before you add it
The standard checks for any shared Bot
Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.
- Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
- Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
- Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
- Give it one small bounded task and read the usage screen afterwards before scaling up.
Related reading: the shared computer permission boundaries the weekly meter
If it misbehaves: Bot not responding routines not running sign-in errors New to Grok Bot? what it is your first task
Attribution
This Bot belongs to its creator, @suddenlyjon ♞. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot, cs68614-hash/awesome-grokbot-templates and kydlikebtc/awesome-grokbot. Row metadata is CC0. Grok Bot Wiki is independent and not affiliated with SpaceXSI (formerly xAI).
Made this Bot? Add a “Listed on Grok Bot Wiki” badge
Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles ↗
Markdown (README)
[](https://www.grokbotwiki.com/bots/buzzkill)
Or promote this template in the labelled Featured row, from $19.