# Token Efficiency

Reduce token waste by 40-60% through anti-sycophancy rules, tool-call budgets, one-pass...

- Repository: https://github.com/rohitg00/pro-workflow (2940 stars)
- Category: AI and agents
- License: see repository
- Last updated: 2026-09-29
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add rohitg00/pro-workflow --skill token-efficiency -g -a claude-code -y`
Codex: `npx skills add rohitg00/pro-workflow --skill token-efficiency -g -a codex -y`
Cursor: `npx skills add rohitg00/pro-workflow --skill token-efficiency -g -a cursor -y`
Gemini CLI: `npx skills add rohitg00/pro-workflow --skill token-efficiency -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add rohitg00/pro-workflow`

## Description

Reduce token waste by 40-60% through anti-sycophancy rules, tool-call budgets, one-pass coding, task profiles, and read-before-write enforcement. Inspired by drona23/claude-token-efficient.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Token Efficiency

Reduce output token waste and prevent iteration cycles that consume context.

## Trigger

Use when:
- Sessions feel expensive or slow
- Output is verbose with filler text
- Claude is re-reading files or iterating unnecessarily
- Setting up a new project for token-efficient work

## Anti-Sycophancy Rules

These patterns waste 30-60% of output tokens:

| Pattern | Example | Fix |
|---------|---------|-----|
| Sycophantic opener | "Sure! Great question!" | Delete. Lead with answer. |
| Prompt restatement | "You're asking about X..." | Delete. Answer directly. |
| Closing fluff | "Let me know if you need anything!" | Delete. Stop after the answer. |
| Unsolicited suggestions | "You might also want to..." | Delete unless asked. |
| AI disclaimers | "As an AI model..." | Delete entirely. |
| Verbose preambles | "I'll help you with that..." | Delete. Start with the action. |

## Tool-Call Budgets

Set explicit budgets by task complexity:

| Task Type | Tool-Call Budget | Wrap-Up At |
|-----------|-----------------|------------|
| Quick fix / lookup | 20 calls | 15 |
| Bug fix | 30 calls | 25 |
| Feature (small) | 50 calls | 40 |
| Feature (large) | 80 calls | 65 |
| Refactor | 50 calls | 40 |
| Exploration / research | 30 calls | 25 |

At the wrap-up threshold: commit progress, assess remaining work, decide whether to continue or start fresh.

## One-Pass Coding Discipline

For simple-to-medium tasks:

1. **Read all relevant files** including tests first
2. **Understand what tests assert** before coding
3. **Write complete solution in one pass**, not incrementally
4. **Run tests once**, if pass, STOP immediately
5. **If fail**: read the error, fix once, retest
6. **Never iterate** more than twice on the same failure, rethink approach
7. **Never refactor, improve, or polish passing code**

## Task Profiles

Switch profiles based on what you're doing:

The rest: https://github.com/rohitg00/pro-workflow/blob/HEAD/skills/token-efficiency/SKILL.md