spend-watch

Analyzes cloud usage across Neon, Vercel, Railway, and GitHub Actions to produce ranked cost recommendations.

714|255|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/aaronjmars/aeon --skill spend-watch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spend-watch
Source: https://github.com/aaronjmars/aeon/tree/main/skills/spend-watch
Command: npx skills add https://github.com/aaronjmars/aeon --skill spend-watch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cloud bills across multiple platforms are hard to attribute and act on: usage data is scattered across Neon, Vercel, Railway, and GitHub Actions, and most tools invent dollar figures where no billing API exists. This Skill pulls per-object usage from each platform, attributes spend to the biggest drivers, root-causes each one, and emits recommendations ranked by real signal (idle %, over-allowance, failure rate) with dollar figures only where the billing API returns real ones.

Core Features & Use Cases

  • Multi-platform attribution: Adapters for GitHub Actions (via gh CLI), Neon, Railway (GraphQL billing), and Vercel rank cost drivers down to the service, branch, route, or workflow level.
  • Honest dollar reporting: Real USD figures appear only when a billing API returns them (Railway currentUsage, Actions overage); everywhere else the recommendation carries its true signal instead of a fabricated estimate.
  • Optional armed mode: With the arm: prefix, the Skill applies safe cost levers such as lowering Neon suspend timeouts, deleting stale Vercel preview deployments, pruning old Actions artifacts, or opening a PR to trim a cron schedule.
  • Use Case: Run a weekly sweep with scope 'all' to get one digest showing real Railway and Actions spend, the top signal-ranked drivers everywhere, and a ranked action list, then re-run with 'arm:neon' to apply the safe Neon fixes automatically.

Quick Start

Ask the agent to run spend-watch with scope 'all' to audit every configured platform and receive a ranked cost recommendation digest.

Frequently Asked Questions about spend-watch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor cloud costs across Neon, Vercel, Railway, and GitHub Actions?

Run spend-watch with an empty or 'all' scope to sweep every platform whose API token is present. It pulls per-object usage from each provider, attributes spend to the biggest drivers, and emits one combined digest of ranked recommendations.

How to reduce GitHub Actions billing costs?

The actions adapter checks your account-wide minutes against the included allowance, attributes usage per repo and workflow, and recommends trims like reducing cron frequency or moving macOS jobs to Ubuntu. Armed mode can delete stale artifacts or open a PR trimming the biggest schedule.

Does spend-watch change my infrastructure automatically?

No, by default it is read-only and only recommends. Mutations require the arm: prefix (for example arm:neon), and even then each adapter re-reads the target's live state before acting and never deletes production deployments or default branches.

Why does the report show no dollar amounts for Neon or Vercel?

Neon's lower plans and Vercel's public API expose no billing dollars, so the Skill reports real signals instead, such as idle-awake percentage or stale-preview count. It never fabricates a dollar figure by multiplying usage by an assumed rate.

What API tokens does spend-watch require?

It uses NEON_API_KEY, VERCEL_TOKEN, and RAILWAY_TOKEN through secretcurl placeholders, plus GH_TOKEN for the GitHub Actions adapter via the gh CLI. Any adapter whose secret is absent skips itself and logs the skip without failing the run.

Can I test the digest without sending notifications?

Yes, append dry-run to the scope variable to build the full digest while suppressing the notify step. This is intended for testing the analysis output before enabling real notifications.