AI Cost-Cutter Skills

10 installable skills that cut your AI bill with proof instead of vibes. Free, MIT.

Every "switch to a cheaper model" tip has the same missing piece: evidence that the cheap path still does your job. These skills close that gap. Each one turns a cost-cutting pattern into a procedure your coding agent runs, and every skill carries a runnable proof block that this repo's CI actually executes on every push and weekly on a schedule. The badge above is real, not decorative. Each skill is distilled from a recipe in the FlowStacks corpus, where the deterministic spine is re-checked by CI so the recipe can't silently rot.

Works in Claude Code, OpenAI Codex, Cursor, and any agent that reads the agentskills.io SKILL.md format.

The idea in one sentence

The reason people overpay for AI isn't missing tooling; it's missing trust in the cheap path. So every skill here ends with a check you can run, not a claim you have to believe.

The skills

Install

One command, any agent (recommended): Vercel's skills CLI auto-detects your coding agent (Claude Code, Cursor, Codex, Copilot, Gemini, and more) and installs into the right place for each:

npx skills add Neeeophytee/ai-cost-cutter-skills

Add --list to preview the 10 skills first, or --skill token-receipts-audit to install just one. (Discoverable on skills.sh.)

As a Claude Code plugin (all 10 skills):

/plugin marketplace add Neeeophytee/ai-cost-cutter-skills
/plugin install cost-cutter@ai-cost-cutter-skills

Manually (pick the skills you want): copy any skills/<name>/ folder into your project's .claude/skills/ directory (or ~/.claude/skills/ for all projects). Codex reads the same format from ~/.agents/skills/.

The one-file version: for the whole approach as passive guidance instead of commands, drop CLAUDE.md (Claude Code) or AGENTS.md (Codex and other AGENTS.md-reading agents) into your project root, or append it to your existing one.

When to reach for which

• The bill is high and you don't know why → token-receipts-audit first, always
• Bulk workload on a premium model → route-cheap-escalate-hard
• Cheap executor + expensive reviewer → advisor-call-budget
• "Can I just switch to the cheap one?" → cheap-swap-guard
• Coding agent re-reads the same files forever → context-diet
• Reasoning model, mostly easy turns → reasoning-effort-throttle
• New model launched, tempted → model-bakeoff
• Everything depends on one hosted model → tested-fallback
• Huge one-time backlog, no budget → free-tier-batch-plan
• Drowning in a reading pile → free-model-triage

See EXAMPLES.md for real prompts.

How verification works (and what it doesn't claim)

Two honest layers:

1. This repo's CI extracts every skill's bash verify proof block and executes it on every push and weekly on a schedule. If a proof stops passing, the badge at the top goes red. No proof, no merge.
2. The upstream recipes at FlowStacks re-run each recipe's deterministic spine (configs, schemas, arithmetic) in CI on every change. The model steps (actual quality, actual per-task cost on your workload) are explicitly fenced: no CI can promise those, so neither do we. Every skill says out loud which part is proven and which part you must measure on your own traffic.

That second sentence is the whole philosophy: a badge should never claim more than what actually ran.

License

MIT. Prices and limits cited inside skills carry their as-of dates; check current pricing pages before relying on them.

_{Maintained alongside awesome-ai-workflows, a list of AI workflows re-checked by CI, finding-unknowns-skills, and FlowStacks, where each recipe carries a machine-verified badge. If this pack saves you money, a star helps the next person find it.}