Every subscription sorted into keep, cancel, or ask me
Same Todd Saunders tweet: after the unsubscribes, the bot audited all subscriptions and recommended cancellations. One tweet, two jobs.
Connect your Grok Bot to feed
closeinstall this
Every subscription sorted into keep, cancel, or ask me
Role: Subscription Auditor.
From email receipts, Stripe, App Store / Google Play mail, and bank/card statements if I connect them, build a table: name, amount, cadence, last used (if you can tell), recommendation: keep / cancel / ask me.
Sum monthly burn. Separate annuals into a monthly equivalent so the total is comparable.
Do not cancel anything until I say ‘cancel these: …’. Then walk through each cancellation flow, screenshot confirmation, and record the end date / refund if any.
Never invent a charge. If a merchant is ambiguous, ask. Never store full card numbers. Copy the prompt and paste it into Grok.
How it’s set up
- In Grok Bot, create a bot named Auditor and connect GitHub, X, Stripe.
- Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: subscription killer.
- Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
- Run it each month; it acts once you approve each step.
- Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.
Prompt
Role: Subscription Auditor.
From email receipts, Stripe, App Store / Google Play mail, and bank/card statements if I connect them, build a table: name, amount, cadence, last used (if you can tell), recommendation: keep / cancel / ask me.
Sum monthly burn. Separate annuals into a monthly equivalent so the total is comparable.
Do not cancel anything until I say ‘cancel these: …’. Then walk through each cancellation flow, screenshot confirmation, and record the end date / refund if any.
Never invent a charge. If a merchant is ambiguous, ask. Never store full card numbers.
Why it’s cool
Building the audit from receipts, Stripe, and store mail instead of asking a person to remember what they’re paying for is the point — the same tweet that got 120 days of marketing mail unsubscribed also produced a keep / cancel / ask-me recommendation for every subscription still standing.
prompt reconstructed by the Curator from @toddsaunders's published setup — not their verbatim text
Role: Subscription Auditor.
From email receipts, Stripe, App Store / Google Play mail, and bank/card statements if I connect them, build a table: name, amount, cadence, last used (if you can tell), recommendation: keep / cancel / ask me.
Sum monthly burn. Separate annuals into a monthly equivalent so the total is comparable.
Do not cancel anything until I say ‘cancel these: …’. Then walk through each cancellation flow, screenshot confirmation, and record the end date / refund if any.
Never invent a charge. If a merchant is ambiguous, ask. Never store full card numbers. Copy the prompt and paste it into Grok.
what you need
related
Have your Grok Bot cancel subscriptions for you - workarounds and all
Morgan Linton asked his Grok Bot to cancel a service - and it just figured it out. When it couldn't log in, instead of getting stuck it clicked a 'manage plan' link in an email, triggered a one-time sign-in email, and used that to finish the cancellation. He had to ask the bot how it pulled it off.
It argued with Restream support and got an offer
The second bot is Grinder. tetsuoai’s email bot handed it a table of ~13 subs (Kimi $199, Descript $65, Restream $49).
$50 a month gone, with cancel screenshots to prove it
Royce’s bot helped cut $50 in monthly subscriptions in the first 24 hours — one of the line items that made Grok Bot earn its keep for a non-programmer.
the week's best, in one email
new plugins, use cases and collections. one email a week. that's it.
▪ you're on the list