Frontier Spend

Use when planning how to spend scarce or expiring access to a premium frontier-tier model (usage-capped, deprecation cliff, "how should I spend my remaining premium-model budget", 2x burn rate, model leaving the plan) — before starting any premium-model session or writing a spend plan.

37 stars 7 forksAI, LLMs & Agents

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add iamneilroberts/claude-skills --skill frontier-spend
Manual install
git clone --depth 1 https://github.com/iamneilroberts/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/frontier-spend ~/.claude/skills/frontier-spend

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Frontier Spend

## Overview

A scarce premium-tier model is a **non-renewable judgment credit**. The only value that
survives the cap or the cliff is what lands in durable artifacts (plans, verdicts,
audits, tests) that a cheaper model executes later. Most agents get "spend on judgment,
not typing" right on their own — the four rules below are the ones they miss.

## The four rules (each one counters a default failure)

1. **Adjudicate, don't author.** Do NOT have the premium model write specs/plans/ADRs
   from scratch — planning is its fastest token burn (practitioner reports: ~35% of a
   usage window on one planning pass). Instead: **cheaper model drafts → an independent
   cross-vendor reviewer audits → premium model adjudicates the disagreements and
   patches.** Same banked artifact, several times more of them per cap. From-scratch
   authoring only after a cheap draft comes back structurally wrong twice.
2. **Ration audits to a named budget.** Comprehensive sweeps feel high-value and are the
   fastest way to exhaust a cap. Pick the audit count up front (default: **two**) and
   name them (e.g. golden-path adversarial review + tech-debt sweep). Everything else
   gets triage-grade attention or none.
3. **Tune the effort slider.** Reduced reasoning effort for triage-grade judgment
   (queue ranking, routine verdicts) — low-effort premium can undercut the mid-tier
   model's cost. Max effort only for the named audits and plan adjudication.
Read the full skill on GitHub

Details

Skill name
frontier-spend
Path
skills/frontier-spend/SKILL.md
Repo updated
21 August 2026

FAQ

What does the Frontier Spend skill do?

Use when planning how to spend scarce or expiring access to a premium frontier-tier model (usage-capped, deprecation cliff, "how should I spend my remaining premium-model budget", 2x burn rate, model leaving the plan) — before starting any premium-model session or writing a spend plan.

How do I install the Frontier Spend skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add iamneilroberts/claude-skills --skill frontier-spend. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Frontier Spend popular?

It lives in iamneilroberts/claude-skills, which has 37 GitHub stars and 7 forks.

Related skills

Brag

37

iamneilroberts/claude-skills

Memorialize something you just built by generating a self-contained "showcase" page for it — a persuasive, good-looking deep dive: what it is, why it's impressive, how it works — with a screenshot if one can be found or captured, and links to related showcase pages. This is the sales/hype-leaning counterpart to /write-post (which drafts a neutral, no-BS technical post); reach for /brag when you want it to sell. Fast by design, like /idea: ask only what's needed, build the page, don't turn it into a project. Triggers on `/brag <subject>`, "brag about this", "make a showcase page for X", "write

Writing & Content

Branch

37

iamneilroberts/claude-skills

Create an isolated git worktree for a task and log it to a shared work journal, so multiple Claude Code sessions run in parallel without racing on HEAD, uncommitted edits, or the index. Subcommands: `list`, `done <slug>`, `update` (heartbeat), `coord <message>` / `coord clear <slug>` (cross-session constraints). Triggers on `/branch`, "start in a worktree", "isolate this work", "parallel session", "heartbeat the journal".

Git & Code Review

Claude Code Best Practices

37

iamneilroberts/claude-skills

Use when asked about Claude Code workflow, prompt caching cost, session economics, CLAUDE.md hygiene, context-window management, plan mode, permission modes, hooks, skills, subagents, checkpointing/rewind, parallel sessions, worktrees, headless/CI usage, the Agent SDK, slash commands, MCP configuration, or "what's the right way to use Claude Code for X". Also use proactively BEFORE suggesting /model, /compact, fast-mode toggle, or editing CLAUDE.md mid-session, since those bust the system cache.

AI, LLMs & Agents

Gemini Review

37

iamneilroberts/claude-skills

Get a second-opinion review of the current diff (or a chosen focus — architecture, security, docs, design, performance, tests) from the Gemini CLI, then present its findings alongside your own analysis. Single-reviewer counterpart to /codex-review and /review-panel; needs the `gemini` CLI installed. Triggers on `/gemini-review [focus]`, "gemini review this", "get a gemini second opinion on this diff".

AI, LLMs & Agents

Evaluate

37

iamneilroberts/claude-skills

Tear down a third-party product/tool/library from a single URL and answer two questions: (1) is the product worth adopting as-is — installed into your Claude Code workflow (a CLI, MCP server, skill, or dotfile) or otherwise kept around — and (2) are there features or code worth lifting into your current repo. Most evaluations are hunting for one of those two wins. It resolves the URL to its source (repo, README, launch post — with Reddit and paywalled-fetch fallbacks), characterizes the product from its docs, clones the code locally when it's open source, then fans out read-only subagents — ea

AI, LLMs & Agents

LLM Tools

37

iamneilroberts/claude-skills

Use when a session is about to bulk-read 3+ files or any single file over ~400 lines, generate predictable boilerplate (tests, fixtures, config scaffolds, doc templates), or compress a long session transcript — and a cheap OpenAI-compatible worker model (Kimi, DeepSeek, OpenRouter, local Ollama) is available via the llm-ask/llm-write/llm-extract CLIs.

AI, LLMs & Agents

Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.