Grokbot TemplatesGrokbot Templates
All use cases

Money

Audit recurring spend with a ledger and human money gate

Teams see what got charged, not which renewals still deserve a decision.

Share

What hurt

Myttle (@xmyttle) rebuilt SpaceXAI's procurement lesson into a stealable desk: connect Invoice → usage → owner → terms → market price → human approval. Keep four states (detected / validated / approved / realized) so "found" never equals "saved." Start with evidence copies (CSV, receipts folder, read-only contracts), one durable ledger row per product, a small deterministic recurrence script, then four narrow detectors (recurrence, usage, overlap, market). Bot chases evidence; humans still own money, contracts, and vendor messages.

What to install or create

Stand up a spend-audit bot with read-only evidence only. Build the ledger fields she lists. Run recurrence in code; let the bot judge messy matches. Queue decisions with next-evidence-needed. Hard stop before vendor contact, plan change, cancel, buy, or any payment credential.

Bots

  • Spend Audit

    Maps recurring charges to owners, usage, and renewal deadlines; queues human decisions.

Plugins

  • None on day one. Follow the first-run steps.

Files

  • Redacted transaction CSV, receipts folder, read-only contracts/invoices, owner list, optional seat/activity exports.

  • Spend ledger sheet/DB with detected→realized status fields.

Routines

  • Weekly: review rows added since last audit; refresh evidence; queue decisions before renewal deadlines.

The prompt

This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.

First run

  1. 1Read https://x.com/xmyttle/status/2096950019756556546 (and the follow-up control-loop note at https://x.com/xmyttle/status/2097082365273104602).
  2. 2Collect evidence copies only — no full card numbers, auth codes, or payment authority.
  3. 3Create one ledger row per product with her fields, including status (detected/validated/approved/realized) and next evidence needed.
  4. 4Detect recurrence with a small script; hand candidates to the bot with receipts, usage, and contracts.
  5. 5Run four narrow detectors: recurrence, usage, overlap, market — never a vague "review my expenses."
  6. 6Human decides cancel / reduce / switch / renegotiate. Bot never messages vendors or moves money.

Approval fence

Never cancel, renegotiate, email a vendor, buy, or touch payment credentials without an explicit human yes. Evidence and recommendations only until then.

What to tweak

Steal the control loop and the four savings states. Company-reported dollar figures are theirs, not yours to claim.

Source

Myttle @xmyttle · Original post

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

Browse templates

Browse team blueprints

Pro pack

Want the full setup, not just the idea?

Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.

See Pro