subscription-audit
Skill0 starsChanged 27 days agoMITView on GitHub
Find every recurring charge in a bank/card CSV export, compute monthly and yearly cost, and recommend keep, cancel or downgrade. Use when the user asks to audit subscriptions, find recurring charges, or cut monthly costs.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- learnaiwithhugo/finance-trackertheir own version, first seen Nov 8, 2026
- razbakov/skillstheir own version, first seen Oct 17, 2026
- Thisisily/momputertheir own version, first seen Oct 15, 2026
- trac3r00/agent-skillstheir own version, first seen Aug 26, 2026
- aakashg/parenting-ostheir own version, first seen Aug 13, 2026
- Itsme23476/everyday-claude-skillstheir own version, first seen Aug 5, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- razbakov/skills★ 4same name
- Thisisily/momputer★ 2same name
- aakashg/parenting-os★ 1same name
- Itsme23476/everyday-claude-skills★ 1same name
- muhammadwaheedairi/Personal-AI-Employee★ 1same name
- learnaiwithhugo/finance-tracker★ 0same name
- trac3r00/agent-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
3
Distinctive
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 15
If Python is available, run python scripts/subscription_audit.py <csv> (the script ships inside this skill folder.
- Distinctive: line 18
Ask the user Keep / Cancel / Downgrade / Unsure for each item.
- Distinctive: line 23
When giving cancel steps, link only the service's official help page, or tell the user to search "[service] cancel subscription …
- Distinctive: line 27
Never ask for bank passwords or log into accounts.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Subscription Audit
Inputs
- One or more CSV exports (ideally 90+ days) with date, description and amount columns. Ask which column is which if headers are unclear.
- Optional: the user's list of subscriptions they know about.
Procedure
- Load the CSVs. Normalize amounts so that charges are positive. Drop transfers, refunds and card payments (descriptions like "PAYMENT THANK YOU", "TRANSFER").
- Normalize merchant names: uppercase, strip store numbers, dates, reference IDs and city/state suffixes. Group by normalized merchant.
- Flag a merchant as recurring when its median interval matches a cadence (weekly 7±1, biweekly 14±2, monthly 30.4±4, quarterly 91±7, yearly 365±10 days), at least 60% of intervals fit that cadence, and amounts are stable. Items varying more than 10% are kept but flagged "variable amount" (utilities). Reject merchants whose amounts swing widely (coefficient of variation > 25%); these are ordinary shopping, not subscriptions. Two charges only = "low confidence". No charge for 1.5× the cadence = "possibly cancelled".
- If Python is available, run
python scripts/subscription_audit.py <csv>(the script ships inside this skill folder; resolve the path relative to this SKILL.md) and review its table instead of computing by hand.
- If Python is available, run
- For each recurring merchant record: cadence, typical amount, last charge date, next expected date (last + cadence), monthly equivalent (weekly ×52/12, yearly ÷12), and yearly cost.
- Mark possible duplicates: two merchants in the same category (e.g., two music services, two cloud storage plans) or the same merchant on two cards.
- Ask the user Keep / Cancel / Downgrade / Unsure for each item. If asked, suggest based on overlap and last-used date. Never pressure.
- Output:
- Table: Merchant | Cadence | Amount | Monthly | Yearly | Next charge | Flag | Decision
- Totals: current monthly/yearly spend, and savings if the decisions are applied
- Cancel checklist ordered by next charge date (soonest first), with a reminder to cancel before that date.
- When giving cancel steps, link only the service's official help page, or tell the user to search "[service] cancel subscription site:[official domain]". Never invent steps.
Rules
- Show your matching assumptions; list "possible recurring" items separately when confidence is low.
- Never ask for bank passwords or log into accounts.
- Not financial advice.
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.