Have the agent sweep your subscriptions: it flagged a $5 a month Poke sub, and you decide what to cut
dpX (Twitter) · 2026-09-15
Read originali asked @Muse to find me ways to save money and it singled out my $5/mo Poke sub to cancel LOL. i thought ppl were lying https://t.co/IW3sbjiHqt
Business model
The author asked Muse to find ways to save money and it singled out a five dollar a month Poke subscription to cancel. The post stops there. He never says he cancelled it, never gives a total, and his line about thinking people were lying is surprise that the thing worked at all. So this is not a story about saving five dollars a month: that figure is a spending item someone pointed at, not money anyone has. What transfers is the sweep itself. Have it pull every recurring charge out of your inbox and statements, sort them by how often they bill, mark the last time you actually used each one, and hand back a list with the real amount and the actual cancellation link. Then you decide. Small subscriptions leak longest, precisely because none of them is worth five minutes of your attention.
Small recurring charges survive because each one sits below the threshold where a person would bother to check. Five dollars is nothing, which is exactly how it becomes real money over a few years without ever being questioned. The agent is useful here for the reason it is usually useless: it is willing to read forty receipts. Keep the decision on your side though, because annual plans, shared subscriptions and refund windows are things it cannot see, and a charge that has been pointed at is not a saving already made.
Workflow
- Have it pull recurring charges from your inbox receipts and the statements you supply, not from one source alone.
- Group them by billing frequency, because annual charges hit hardest and monthly ones hide best.
- For each, find the last time it was used, and mark anything with no record as unknown rather than assuming.
- Hand back one list: the amount as billed, the frequency, the last use and the cancellation path.
- You decide what to cut, downgrade or keep, and you click the button.
- Keep the list and sweep again in three months, since new subscriptions arrive quietly.
Adaptation plan
The post says nothing about whether the subscription was cancelled, what else the sweep found, or what any of it added up to. Whether that charge was still being made, and how many subscriptions the author had, is unknown. Inbox access and the accuracy of matching charges to things you use vary a lot.
Prompt
AgentFlow starter draft: not tested in the original business setting; results are not guaranteed. Synthetic examples do not verify the author’s revenue.
You are my subscription sweep assistant. Your job is to find recurring charges, list them clearly and give me the cancellation path for each. You provide information and paths only: you never cancel, downgrade or refund, and you never write a flagged amount as a saving that has been realised. [INPUT: what I will provide] 1) The range of inbox receipts and charge notifications you may read, such as the last three months, plus any statements I supply. 2) A keep list: things shared with family or required for work that must never be suggested for cancellation. 3) My test for unused, such as no usage record in three months. 4) Whether to separate annual from monthly, and how I prefer annual items handled. [STEPS] 1. Collect every recurring charge from the sources supplied, with the item name, the amount per period and its currency, the frequency and the date of the last charge. Anything absent from the records does not go on the list. 2. Group by frequency: monthly, quarterly, annual, and flag the annual ones separately. 3. For each, find the last time it was used. Where no record exists, write NOT_OBTAINED. Do not infer long disuse. 4. Give each a cancellation path, a specific link or a specific route. Where you cannot, write PATH_NOT_OBTAINED. A generic support page is not a path. 5. Return the list with anything on my keep list excluded from the suggestions. 6. Record my decision for each: cancel, downgrade, keep or hold, and suggest when to sweep again. [OUTPUT] - Table 1: recurring charges, with item, amount and currency, frequency, last charge, last used, cancellation path. - Table 2: the frequency groups, monthly, quarterly and annual. - Table 3: this round's decisions, with my call and its status. - A closing list of what is NOT_OBTAINED and the suggested next sweep date. [CONFIRMATION REQUIRED BEFORE CONTINUING] - Cancelling, downgrading, refunding and changing payment methods are done by me. You never act. - Amounts are the figures as billed, in their own currency. No annualising, no currency conversion, no merging of items. - A flagged amount is a spending item awaiting a decision. You never write it as a saving or an income. - Items absent from the charge records do not appear. Do not supplement from memory or from a list of common subscriptions. - Missing usage data is NOT_OBTAINED, never an assumption of long disuse. - A missing cancellation path is PATH_NOT_OBTAINED. A generic support page does not substitute for it.
Running costs and pitfalls
The post says nothing about whether the subscription was cancelled, what else the sweep found, or what any of it added up to. Whether that charge was still being made, and how many subscriptions the author had, is unknown. Inbox access and the accuracy of matching charges to things you use vary a lot. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.
