agentsclimarketplace

Token efficiency

Skill JoaoEquer/Oficina/skills/token-efficiency

A lean agent harness for AI-assisted development — NestJS + TypeScript + Prisma + PostgreSQL. Skills, rules and commands extracted from real projects.

Install
npx -y skills add JoaoEquer/Oficina --skill token-efficiency

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Reducing LLM token consumption in AI-assisted development sessions — RTK setup (CLI output compression via hook), session management (/clear, /compact, /rewind, named resumes), model tiering, and complementary habits. Use when setting up a new machine or project for agent work, when sessions are hitting context limits or rate limits too fast, when API costs are a concern, or whenever the user mentions tokens, context window, RTK, session cost, checkpoints, or resuming a session.

SKILL.md

4.8 KB, as published. Nobody here has run it

Token efficiency

Tokens are the working memory of the session. Every verbose command output gets re-read on every subsequent turn, so waste compounds: a 2,000-token git diff costs ~20,000 tokens over the next 10 turns. Two fronts: tooling (RTK) and habits.

RTK (Rust Token Killer)

rtk-ai/rtk is an open-source CLI proxy (single Rust binary, Apache 2.0) that compresses command output before it reaches the context window — 60–90% savings on test runners, git operations and package managers. It runs locally and hooks into the agent's official extension points (Claude Code PreToolUse hook); it does not touch API traffic.

Setup (once per machine)

# Install (official script; on Windows, native binary works since v0.37.2)
curl -fsSL https://raw.githubusercontent.com/rtk-ai/rtk/refs/heads/master/install.sh | sh

# Activate for your harness — hook-only avoids extra per-turn context
rtk init -g --hook-only        # Claude Code
rtk init -g --gemini           # Gemini CLI
rtk init -g --agent cursor     # Cursor

Restart the agent afterwards. The hook rewrites Bash calls transparently (git status → rtk git status); the agent doesn't need to know RTK exists. Prefer --hook-only: the alternative injects an RTK.md into context on every turn, which spends tokens to save tokens.

What it actually covers (calibrate expectations)

  • Big wins: test runners showing failures only (pytest, vitest, cargo test — 90%+), git diff/log/status, package manager install noise, tsc/lint output grouped by file.
  • Not covered: the agent's native Read/Grep/Glob tools bypass the Bash hook. In read/edit-heavy sessions RTK has little to intercept — that's expected, not broken.
  • Verify it's working: rtk gain shows accumulated savings; rtk discover finds commands you ran that could have been compressed.
  • Failure safety: when a command fails, RTK saves the full unfiltered output to disk so nothing important is lost.

Habits that save more than any tool

  • Ask for scoped output: git log -n 5 beats git log; run the failing test file, not the whole suite.
  • Don't paste what the agent can read: reference file paths instead of pasting file contents into the prompt.
  • One domain per session: long mixed sessions accumulate stale context; a fresh session with a good CLAUDE.md/AGENTS.md beats a bloated one.
  • Keep context files lean: the project's AGENTS.md is re-read constantly — it pays rent on every turn. If a section isn't changing behavior, cut it.

Session management

  • /clear between unrelated tasks. A session accumulates every file read and every dead end along the way; /clear starts the next task without dragging that weight. Prefer it over continuing one thread across unrelated work.
  • /compact for a long session you still need. Summarizes history to free up context without losing the thread — use when one task genuinely has to keep going past the point where tool output dominates the window.
  • /rewind to back out of a wrong turn. Rolls the conversation and/or code back to a checkpoint — cheaper than manually undoing several turns of accumulated edits.
  • /rename <name> + claude --resume <name> to give a long-running task a memorable session instead of hunting through the claude --resume picker.
  • /context shows what is actually filling the window — check it before assuming a slowdown is the model's fault rather than a bloated AGENTS.md or an unnecessarily wide file read.
  • Session transcripts live in ~/.claude/projects/<path>/ and are pruned after 30 days by default (cleanupPeriodDays in settings.json). Don't treat them as permanent history — the delivery log in docs/log/ is the permanent record (git-workflow).

Model tiering by leverage

  • Strong model plans, mid-tier model executes. Spend the highest-capability model on exploring the codebase and producing the plan; a faster/cheaper model carries out an already-approved, well-specified plan just as well, for a fraction of the tokens.
  • Never the inverse. A weak model producing the plan compounds mistakes silently through every step that follows; a weak model executing a plan a strong model already approved just executes — review the diff either way.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.