subscription-audit
Skill0 starsChanged 3 months agoMITView on GitHub
Finds the recurring charges (subscriptions) hiding in a bank or credit-card CSV, tells you the true monthly and yearly cost, and flags the ones that look forgotten — a free trial that started charging, or a service that quietly kept billing after you stopped using it. Reads a statement you exported yourself; no bank login, no third-party service, fully offline and deterministic.
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
- daytrader1981/subscription-audit-skilltheir own version, first seen Oct 20, 2026
- razbakov/skillstheir own version, first seen Oct 17, 2026
- Thisisily/momputertheir own version, first seen Oct 15, 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
- daytrader1981/subscription-audit-skill★ 0same name
- learnaiwithhugo/finance-tracker★ 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.
In this repository69 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/AGENTS.mdAGENTS.md
- skills/ultimate-browsing/engine/AGENTS.mdAGENTS.md
- 3d-designSkill
- algorithmic-artSkill
- api-testerSkill
- apple-suiteSkill
- appshotSkill
- astra-initSkill
- blindspotSkill
- changelog-genSkill
- claim-auditSkill
- code-reviewSkill
- comment-checkerSkill
- context-budgetSkill
- cron-auditSkill
- css-pro-tipsSkill
- designSkill
- diff-reviewSkill
- doc-readerSkill
- domain-modelingSkill
- env-gateSkill
- ext-scaffoldSkill
- gate-graphSkill
- gh-address-commentsSkill
- gh-fix-ciSkill
- git-masterSkill
- graph-toolsSkill
- grillingSkill
- herdrSkill
- image-genSkill
- json-diffSkill
- linus-levelSkill
- log-analyzerSkill
- log-deviationSkill
- lsp-setupSkill
- merge-quizSkill
- nbj-write-clearlySkill
- net-probeSkill
- open-loopsSkill
- portfolio-auditSkill
- pro-reviewSkill
- proxmox-veSkill
- remove-ai-slopsSkill
- repo-auditSkill
- resume-auditSkill
- sec-headersSkill
- secret-gateSkill
- seo-auditSkill
- session-finderSkill
- session-handoffSkill
- session-rulesSkill
- skill-auditSkill
- skill-creatorSkill
- skill-decaySkill
- skill-optimizerSkill
- skill-pickerSkill
- skill-syncSkill
- social-researchSkill
- sys-healthSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 37
No bank login, no Plaid, no cloud.
- Very specific: line 47
A budget guardrail on a schedule: Run it monthly with --budget N.
- Distinctive: line 51
Not for: categorizing one-off spending, forecasting, or replacing a real budgeting app.
- Very specific: line 72
Put it on a leash: Add --budget 80 to fail (exit 1) when recurring spend passes $80/mo, and drop that into a monthly cron so creep gets …
“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
Re-read a year of statements the way no human bothers to.
Overview
Subscriptions are engineered to be invisible. Each charge is small, they land on
different days, the merchant name is ADOBE *CREATIVE CLOUD 800-833 instead of
"Adobe", and nobody sits down to re-read twelve months of a bank statement by
hand. So the free trial that started charging, the gym you stopped going to, the
app you used once — they just keep billing.
subscription_audit.py is the re-reader. Feed it a CSV you exported from your
bank or card and it:
- finds the recurring charges by clustering repeat payments to the same merchant at a regular cadence (weekly / monthly / quarterly / yearly), while ignoring one-off spending like groceries, gas, or a flight;
- normalizes messy merchant names (
AMZN Mktp US*RT4G9→amazon, store numbers and auth codes stripped) so the same service groups together; - reports the true cost — monthly and annualized — across everything it found;
- flags review candidates: a subscription whose expected next charge is well
overdue (
STALE), or one whose first non-zero charge was substantially smaller than later charges (trial→paid).
No bank login, no Plaid, no cloud. It reads a file you already have, is pure standard library, and is deterministic — the same statement always gives the same answer. A ruler for your recurring spend, not a budgeting app.
When to use
- The monthly "where does it go?" question. Export a statement, run the tool, see the whole subscription stack ranked by cost in one screen.
- A cancellation sweep. The
STALEandtrial→paidflags are your cut list — the tool even totals what cancelling the stale ones saves per year. - A budget guardrail on a schedule. Run it monthly with
--budget N; it exits non-zero when detected recurring spend creeps past your line, so a cron job or CI step can ping you when subscription creep sets in.
Not for: categorizing one-off spending, forecasting, or replacing a real budgeting app. It answers exactly one question — what am I paying for on repeat?
The method
- Export a statement. From your bank or card, download transactions as CSV (any date range; the more months, the better the cadence detection). Most exports have a date, a description/merchant, and an amount column — the tool sniffs these by header name or by content, so you usually need no flags.
- Run it.
python scripts/subscription_audit.py statement.csv # or pipe it: cat card.csv | python scripts/subscription_audit.py - - Read the stack. Subscriptions are listed heaviest-first with their monthly cost, per-charge amount, cadence, and last-seen date. The footer gives the total monthly and yearly burn.
- Review the flags.
⚠ STALEmeans no charge appears within the configured interval;trial→paidmeans the first non-zero charge was smaller than later charges. The summary estimates the yearly cost of the stale entries. Confirm each charge with the provider before cancelling it. - Put it on a leash. Add
--budget 80to fail (exit 1) when recurring spend passes $80/mo, and drop that into a monthly cron so creep gets caught early.
Useful flags: --json (machine-readable, for a cron/agent to consume),
--min-charges N (how many hits before a merchant counts as recurring; default 3),
--stale-days N (grace period past the expected next charge before flagging),
--currency € (display symbol).
Anti-patterns
- Feeding it two months and expecting miracles. Cadence detection needs at least three hits of a merchant. A short statement will under-report — export a longer range.
- Trusting
STALEas "already cancelled". Stale means no recent charge in this file — it might be an annual plan that just isn't due, or a charge outside your export window. It's a prompt to check, not proof it's dead. - Treating the monthly total as your whole budget. This is recurring spend only; it deliberately ignores groceries, gas, and one-offs. It's not a full budget.
- Cancelling on the merchant string alone.
githubandgithub sponsorsmay be two different things collapsed by name normalization — glance at the example description before you cancel.
Example
$ python scripts/subscription_audit.py statement.csv --budget 100 --stale-days 20
Subscription audit
======================================================================
monthly each cadence last merchant
----------------------------------------------------------------------
$ 54.99 $ 54.99 monthly 2026-06-15 adobe creative cloud
$ 15.49 $ 15.49 monthly 2026-06-03 netflix
$ 10.99 $ 10.99 monthly 2026-07-05 spotify usa ny
$ 10.00 $ 10.00 monthly 2026-03-28 planet fitness ⚠ STALE
$ 4.00 $ 4.00 monthly 2026-04-18 github ⚠ STALE
----------------------------------------------------------------------
$ 95.47 monthly across 5 subscriptions (≈ $1,146/yr)
⚠ 2 look forgotten (no charge in a while): cutting them saves $14.00/mo (≈ $168/yr).
· planet fitness — last seen 2026-03-28 (99d ago), $10.00/mo
· github — last seen 2026-04-18 (78d ago), $4.00/mo
budget $100.00/mo → OK ($95.47 detected)Groceries, gas, a flight, and an Amazon order in the same statement were correctly ignored — only the things that recur on a rhythm were surfaced.
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.

