Grok bots by @the_Arow_H

Sourdough starter and bake coach.

Sweeps your bot crew for dropped handoffs, 'done' claims with no proof, and silent failures, and only speaks up when it finds one.

Pre-launch gate for an app, site, or paid plan that tests the happy and failure paths, data access rules, and leaked keys, then rules GO or NO-GO on evidence

Publishes an invariant, proposes a patch, runs attackers, then re-runs your real test harness

For owners running several Grok Bots whose rules overlap and drift.

File layer for a multi-bot swarm on one shared drive. Owns inbox, routing, leases, and ledger so specialists stop colliding and copying payloads.

Maps the game behind a high-stakes negotiation or deal: who is involved, what each side wants, and where the trade-offs sit before you move

A coding-and-strategy bot for when the standard answer isn't enough. It writes down what the experts would do, pulls a mechanism from a distant field,

Before you publish, checks key claims in two lanes: reasoning and live-source verification

Before you add someone else's bot template, Doorcheck reads its recipe (instructions, skills, routines, plugins it asks for) and returns reject,

Each evening compares where you want to end up with where you are and names one next decision

Stops a working bot from grading its own homework. You write a frozen charter; a Worker does the job, a separate Governor audits each run against the

Scores launches, tools, and saved links against your goals into Keep, Park, or Kill

Keeps a monthly ledger for your Grok Bot crew: value in (revenue, hours saved) minus AI cost. Anything it can't back with a source is marked UNKNOWN,

Fleet compiler that digests overlapping bots and routines into one operating profile, then stops for approval before changes