Grokbot TemplatesGrokbot Templates
All use cases

Engineering

Private GitHub backup for Grok Bot computers

“It’s on the computer” is not a backup.

Share

What hurt

Nathan Glass treats bot computers as shops that need disaster recovery. He pastes a backup brief to a Grok Bot so it builds a private GitHub sync of SOPs, skills, memory, profiles, and routines — never secrets — with a twice-daily quiet push.

What to install or create

Author-quoted backup prompt. Shared SOPs live in one project every bot joins. Working copy on the bot computer stays source of truth. Exclude tokens, cookies, transcripts, plugin caches. RESTORE.md + password-manager path checklist. Git restores knowledge; you still recreate agents, rejoin projects, and re-auth connectors after a wipe.

Bots

  • Backup Clerk

    Maintains the private GitHub mirror and twice-daily sync. Never touches secret values.

Plugins

  • Browser

    Optional

Files

  • Private GitHub repo with RESTORE.md and secret-path checklist (paths only).

Routines

  • Twice-daily sync (morning + evening local). Push only when files changed; stay quiet otherwise.

The prompt

Author-quoted backup brief

Quoted from Nathan Glass’s Article via https://x.com/nathanglass/status/2096390637163589808

Last line is our approval fence: Never send, post, spend, or buy without my explicit yes.

Create a private GitHub backup of this Grok Bot computer for disaster recovery. Include: ops/SOP markdown projects, custom skills/workflows, shared user memory, each agent’s profile + routines + memory (no secrets), and non-secret tooling scripts. Add RESTORE.md explaining how to restore. Exclude: all tokens/OAuth/connector secrets, Chrome cookies, chat transcripts, plugin caches. Use a private repo I create (or create one if you can). Working copy on the bot computer stays source of truth. Set a twice-daily sync (morning + evening in my timezone) that pushes only when files changed; stay quiet when unchanged. Also give me a checklist of secret file paths to store in my password manager (values never in git or chat).

Never send, post, spend, or buy without my explicit yes.

First run

  1. 1Read https://x.com/nathanglass/status/2096390637163589808 and the Article “How to back up your Grok Bots”.
  2. 2Put shared SOPs in one project every bot joins.
  3. 3Paste Nathan’s backup brief into a Backup Clerk bot (quoted on this page). Prefer a private repo you create.
  4. 4Hang the twice-daily sync routine. Confirm secrets stay out of git; keep values only in your password manager using the path checklist.
  5. 5After a wipe: recreate agents from profiles, rejoin projects, re-auth connectors, then drop secrets into the listed paths.

Approval fence

Create only a private repo. Never commit tokens, cookies, or chat transcripts. Confirm before any force-push or wipe.

What to tweak

Backup knowledge and routines, not OAuth. Twice-daily sync only when files change. Keep secret values out of git and chat.

Source

Nathan Glass @nathanglass · Original post

Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.

Browse templates

Browse team blueprints