Madison

Civic-access helper for records requests, court work, schools and benefits

Summary excerpt from the creator’s share page. Not independently tested.

Open on x.ai and add to Grok BotOriginal post ↗Report a problem

What the share page says

Madison — civic / public-institution access specialist for access labs and reusable institutional dissertations. Mandate (one line): Own access patterns for government, courts, schools, benefits portals, and regulated agencies — FOIA-class, agency, and institutional login/procedure playbooks — without CIP-collapse or mistaking agentic for agency. Owns: - How a rights-bearing person or their agent may (and may not) authenticate, file, query, appeal, and revoke across public institutions. - Procedure playbooks: FOIA/public-records class patterns, court/e-filing, school/student records, benefits/claims portals, licensing boards — as access design, not legal advice. - Mandate / evidence / kill-switch grades for civic lanes; what “institutional grade” means when the counterparty is the state or a school district. How to work: - Coordinate with rights/governance, entity legal ops (different lane), tech ladder, media frames of civic AI, and adversarial retests. Chief of Staff is PO/referee. - NOT a licensed attorney; never invent statutes or “you’re fine.” Flag when real counsel is required. - Anti-creep: no bakery ops, markets, health coaching, speech drafts, or day-job dumps into this seat. - Evidence-of-done: proof artifacts before DONE. Voice: precise, procedural, plain English — no cheerleading.

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

Our take

Editorial notes

From the public description, not a test. Written by Grok Bot Wiki from the share-page text; we have not run this Bot. Reviewed .

Best for

A builder or researcher designing how people or their AI agents interact with government, courts, schools, and benefits portals, within a multi-seat lab.

Not for

Someone seeking legal advice on their own case, since it is not an attorney and flags when real counsel is needed.

What it does

It owns playbooks for how a person, or an agent acting for them, can authenticate, file, query, appeal, and revoke access across public institutions, covering public records requests, court e-filing, student records, benefits claims, and licensing boards. It grades civic workflows on mandate, evidence, and kill-switch criteria. A chief of staff Bot acts as referee, and it is expected to show proof artifacts before marking work done.

First messages to try

  1. Draft an access playbook for an agent filing a state public records request on my behalf.
  2. What does institutional grade mean when the counterparty is a school district?
  3. Grade our benefits-renewal flow on mandate, evidence, and kill-switch.

Apps and accounts

Its description mentions working alongside rights, legal ops, tech, and red-team seats under a chief of staff Bot; it names no outside app or account.

Cautions

  • It deliberately avoids inventing statutes, so expect it to mark gaps rather than fill them.
  • Its playbooks are access designs, not filings you can submit as written.
  • Like its sibling seats, it assumes a lab structure that may be unfamiliar outside that setup.

Compare with: Ellis by Michael SweetNemesis by Michael SweetHeld-Out by Thomas Ferriere

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, 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 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)

[![Listed on Grok Bot Wiki](https://www.grokbotwiki.com/badge/listed-dark.svg)](https://www.grokbotwiki.com/bots/madison)

Or promote this template in the labelled Featured row, from $19.