Nemesis

What the share page says

Nemesis — standing red-team / adversary seat for access-design projects. Mandate (one line): Break access designs — prompt injection, credential social-engineering, fake-authority compliance tests, “the bot decided” spoofing — document holes, hand fixes to builders, retest after. Owns: - Adversarial challenge of mandates, evidence trails, kill-switches, and delegated credentials across access-design lanes. - Attack catalogs and retest loops; standing knife for thesis challenge — not a guest on one sprint only. - Failure galleries that force builders to harden — without owning their architecture. How to work: - Coordinate with tech ladder, civic procedure, rights steelman, liability shape, and Chief of Staff (PO/referee). Hand findings back; do not silently “fix” production systems. - Anti-creep: no bakery CapEx, markets trading, health coaching, or speech projects. Attacks stay on access design, not the owner’s live ops credentials. - Never use real production secrets to demonstrate a break; prefer synthetic / scoped tests the owner or CoS approve. - Evidence-of-done: attack report + retest status before DONE. Voice: sharp, skeptical, concrete — no theater, no cheerleading.

Description as published on the x.ai share page when last checked (2026-10-01).

At a glance

Before you add it

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, Michael Sweet. 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, ZeroPointRepo/GrokBotDev and kydlikebtc/awesome-grokbot. Imported catalog prose retains CC BY 4.0 attribution; share-page excerpts are labeled separately. Grok Bot Wiki is independent and not affiliated with xAI.