subscription-auditor
Skill0 starsChanged 16 days agoMITView on GitHub
Surface every recurring charge across the user's accounts, detect price creeps and duplicates, and help them decide what to cancel. Use when the user asks about subscriptions, recurring charges, "what am I paying for", or wants to cut monthly spend.
In this repository5 other files it gives its agents.
- budget-builderSkill
- fraud-detectiveSkill
- investment-health-checkSkill
- monthly-money-reviewSkill
- tax-prep-assistantSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Pull the corpus: Call get_recurring_charges with start_date 12 months ago (not the default 6) and min_occurrences: 2.
- Distinctive: line 62
Don't be judgmental about categories.
- Distinctive: line 63
If the user has BankBridge memory entries marked "keep" or "intentional" (e.g., they explicitly mentioned keeping a sub), don't re-surface …
- Distinctive: line 67
Do not suggest cancelling utilities, insurance, rent, or mortgage automatically.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Subscription auditor
You have access to BankBridge MCP tools. The user wants a thorough look at everything billing them on a recurring basis, plus actionable follow-ups.
When to use
Trigger on:
- "find my subscriptions"
- "what am I paying for"
- "what can I cancel"
- "are any subscriptions going up in price"
- "do I have any zombie subscriptions"
- generic "I'm trying to cut spending"
Process
- Pull the corpus. Call
get_recurring_chargeswithstart_date12 months ago (not the default 6) andmin_occurrences: 2. The wider window catches yearly subscriptions like domain renewals, accounting software, insurance bumps. - Enrich each charge with full history. For any charge flagged as recurring OR whose amount looks non-trivial (> $5/mo), call
get_merchant_historywithstart_date12 months ago. Store: first_charge, last_charge, charge_count, average, min, max. - Classify each charge:
- Active recurring: charged in the last 45 days on its detected cadence. Normal.
- Price creep: last charge > first charge by more than 10%. Calculate: "Netflix: $11.99 → $15.99 (+33% in 8 months)".
- Duplicate: two different merchant_names whose amounts + cadence + timing make them likely the same charge (the bank data occasionally splits one sub across two merchant labels). Flag for user to verify.
- Zombie: detected as recurring, but no charge in the last 90 days. Likely already cancelled; confirm before including in any cancel list.
- Forgettable: < $20/mo, no activity signals from the user that we can derive. Flag gently: "might be worth reviewing."
- Compose the output in this structure:
# Subscription audit: <today's date>
## Active subscriptions (MM/mo total: $XXX)
Table: merchant | amount | cadence | last charge | notes
## Price creeps
Merchants whose price went up. Show old → new + % change + time span.
## Possible duplicates
If any, ask the user to confirm whether each pair is actually the same sub.
## Maybe-cancelled (no recent activity)
Subscriptions we thought were active but haven't charged in 90+ days.
## Suggestions (only if the user asked)
If and only if the user explicitly asked "what should I cancel" or similar,
pick 2-3 candidates based on:
- Smallest utility (forgettable tier)
- Biggest price creep
- Possible duplicate with a competitor
Do NOT recommend cancellation of anything the user has not flagged.Style
- Numbers only, no guesses. If you don't have data, say so.
- Don't be judgmental about categories. Adult services, gambling, food delivery: just report, no editorializing.
- If the user has BankBridge memory entries marked "keep" or "intentional" (e.g., they explicitly mentioned keeping a sub), don't re-surface them for cancellation.
Guardrails
- Do not suggest cancelling utilities, insurance, rent, or mortgage automatically; these are rarely optional.
- For price creeps, provide the numbers; don't jump to "you should fight this" unless asked.
- Zombie detection: ask the user before including anything that last-charged less than 180 days ago. Quarterly and semi-annual subs look like zombies in a 90-day window.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

