← ClaudeAtlas

token-economylisted

Token and cost control for coding agents — context and cache hygiene, batching, subagents for mechanical work, escalation, session measurement, guardrails, RTK/CodeGraph audit. Use when saving tokens, cost or context.
ralvarez-ai/ralvaskills · ★ 4 · AI & Automation · score 77
Install: claude install-skill ralvarez-ai/ralvaskills
# Token Economy Spend tokens where they buy accuracy and nowhere else. Most waste is not long replies: it is bytes that enter the context once and are re-sent on every later turn, caches paid twice, subagents that inherit a huge context, retries on a model out of its depth, and sessions that carry three unrelated tasks. Two modes: **working rules** (sections 2-7, 10) and **measure and audit** (section 9). Templates in [RECIPES.md](RECIPES.md); tool notes in [TOOLS.md](TOOLS.md); Claude Code settings and hooks in [GUARDRAILS.md](GUARDRAILS.md). Reply-style compression is [caveman](../caveman/SKILL.md); how skills get imported into a project is [rsk-guide](../rsk-guide/SKILL.md). ## 1. When to invoke - **Measure / audit / setup** — "where did my tokens go", a surprising bill, new machine or project, installing context-mode, RTK or CodeGraph, sessions hitting limits early. - **Working** — before a broad exploration, before a refactor, audit or edit that repeats over many files, when choosing a model or subagent, before polling a job, when a session has grown long or drifted across tasks, when a cheap model starts looping. - **Not this skill** — "just be terse" is [caveman](../caveman/SKILL.md). ## 2. Where tokens go Ranked by what they usually cost over a session: 1. **Resent context.** Every request re-sends the whole conversation, so cost grows with turns x context: a 5k-token read on turn 3 of 40 is paid ~37 more times. Caching makes repeats cheaper, not fre