Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/sonichi/sutando/subscription-scannernpx skills add sonichi/sutando --skill subscription-scannergit clone --depth 1 https://github.com/sonichi/sutandoWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/sonichi/sutando/subscription-scanner)<a href="https://agentmods.dev/skills/sonichi/sutando/subscription-scanner"><img src="https://agentmods.dev/badge/skills/sonichi/sutando/subscription-scanner.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00876 |
| Opus 5 | $0.00000 | $0.00438 |
| Sonnet 5 | $0.00000 | $0.00175 |
| Haiku 4.5 | $0.00000 | $0.00088 |
Grade A, and why
subscription-scanner scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Subscription Scanner
Scans Gmail for active paid subscriptions and tracks them over time. Surfaces additions / cancellations between scans.
Usage
The scan is agent-driven, not script-driven, because Gmail access lives in the Claude Code MCP layer (not in Python). The proactive-loop or owner-on-demand fires the scan via:
/scan-subscriptions
…or the cron job below invokes the agent with the scan-prompt.md body verbatim.
Files
scan-prompt.md— the prompt text the agent runs to perform a scan. Updates here propagate via the cron config. Personalize this file before first use — the third Gmail-query line names specific senders tied to one user's actual subscriptions (Apple, Spotify, Anthropic, OpenAI, Netflix, Adobe, GitHub, 1Password, NYT, WSJ, Disney+, Hulu, Tesla insurance, Xfinity, …). Edit thefrom:list to match your subscriptions, or the scan will miss vendors not on the default list.state/subscriptions.json— current list (gitignored — contains personal financial data)state/history/<YYYY-MM-DD>.json— snapshots, for diff (also gitignored)
State schema
{
"last_scan": "ISO8601 timestamp",
"subscriptions": [
{
"vendor": "Apple iCloud+ 2TB",
"category": "Storage|Streaming|Connectivity|Insurance|Software|Membership|Other",
"amount": 9.99,
"currency": "USD",
"frequency": "monthly|annual|other",
"account": "[email protected] or family member name",
"last_charged": "YYYY-MM-DD",
"next_charge": "YYYY-MM-DD or null",
"status": "active|cancelled|uncertain",
"source_sender": "email From: address that established this",
"notes": "free-form caveats / corrections"
}
],
"scan_history": [
{
"date": "ISO8601",
"active_count": <int>,
"added": ["vendor names"],
"removed": ["vendor names"],
"amount_changed": [{"vendor": "...", "from": <num>, "to": <num>}]
}
]
}
How /paidsubscriptions reads this
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 77 lines · 0 tokens per session scan A 4feefb98f39c
subscription-scanner is a skill published in the GitHub repository sonichi/sutando (391 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 876 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
contacts
Manage contacts, communication channels, access control, and invite links.
gmail
Manage Gmail email — drafting, sending, organizing, filters, vacation replies, and inbox analysis.
app-builder
Build and edit small, personal visual tools and artifacts — dashboards, trackers, calculators, data visualizations, charts, simple landing pages, and slide decks the user wants for THEMSELVES. This is the right skill whenever the user asks to "visualize this," "make a chart," or "build an artifact" for their own use…
assistant-migration
Migrate from ChatGPT, Claude, OpenClaw, Hermes, Manus, and other AI assistants into Vellum by inspecting their data exports, conversation archives, files, prompts, custom instructions, memory, saved memories, tools, GPTs, workflows, integrations, and relationships, then mapping as much as safely possible into Vellum…
guardian-verify-setup
Set up channel verification for phone, Telegram, Slack, Discord, or email channels via outbound verification flow.
media-processing
Ingest and process media files (video, audio, image).