token-efficiency · rohitg00 — Claude Code skill: what it does, how to install
token-efficiency cuts conversational fluff, caps tool executions per task, and stops Claude Code from repeatedly editing working implementations.
MIT ★ 2,966 updated 2026-09-29
/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflowWhat token-efficiency does
This skill strips conversational filler that inflates token usage. It removes apologetic disclaimers, sycophantic openers, and unrequested suggestions so Claude Code delivers direct answers or clean code immediately. All output is forced into standard ASCII characters to avoid smart quotes and unicode clutter.
Operation relies on distinct profiles for coding, data analysis, and agent workflows alongside tiered tool budgets. A small feature gets a ceiling of 50 tool calls, while research is capped at 30. A strict one-pass rule requires reading related files and test assertions first, writing the complete solution, running tests once, and stopping immediately when tests pass.
The rule prohibiting refactoring on passing code prevents spontaneous rewrites, meaning secondary cleanups require an explicit prompt.
What it helps with
- trim conversational filler and AI disclaimers from responses
- enforce tool-call limits according to task complexity
- stop redundant iteration loops on code that already passes tests
- prevent writing or modifying files without reading them first
Example prompts for the agent
- Fix the token expiration bug in
auth.tsfollowing the token-efficiency rules. - Generate the summary table for test coverage using the analysis profile.
- Implement the parser in
parser.tsin a single pass based on assertions inparser.test.ts.
How to install token-efficiency
1Plugin marketplace
/plugin marketplace add rohitg00/pro-workflow/plugin install pro-workflow@pro-workflowThis installs the whole pro-workflow plugin with all its skills
2Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill token-efficiency -a claude-code3Manually: put the files in place
~/.claude/skills/token-efficiency/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/token-efficiency/
1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill token-efficiency -a codex2Manually: put the files in place
.agents/skills/token-efficiency/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill token-efficiency -a cursor2Manually: put the files in place
.cursor/skills/token-efficiency/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install rohitg00/pro-workflow skills/token-efficiency2Manually: put the files in place
.github/skills/token-efficiency/SKILL.md1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill token-efficiency -a gemini-cli2Platform CLI
gemini skills install https://github.com/rohitg00/pro-workflow --path skills/token-efficiencyManually: put the files in place
.devin/skills/token-efficiency/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about token-efficiency
How do I install token-efficiency in Claude Code?
Add the marketplace source by running /plugin marketplace add rohitg00/pro-workflow, then run /plugin install pro-workflow@pro-workflow. Alternatively, install it with npx skills add rohitg00/pro-workflow --skill token-efficiency -a claude-code.
What does token-efficiency do?
It enforces direct answers without filler phrases, restricts file edits to files already inspected, and sets tool-call limits between 20 and 80 calls depending on task scope.
What is the one-pass coding discipline in this skill?
Claude Code reads existing tests first, writes the implementation once, verifies test results, and immediately halts once the test suite passes without refactoring.
Source text
SKILL.md · MIT
--- name: token-efficiency 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. --- # 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: ### Coding Profile - Return code first, explanation after (only if non-obvious) - Simplest working solution, no over-engineering - Read file before modifying — always - No docstrings on unchanged code - No error handling for impossible scenarios - State bug, show fix, stop ### Agent/Pipeline Profile - Structured output only: JSON, bullets, tables - No prose unless targeting a human reader - Every output must be parseable without post-processing - Execute task, do not narrate actions - Never invent file paths, API endpoints, or function names - If unknown: return null or "UNKNOWN", never guess ### Analysis Profile - Lead with finding, context and methodology after - Tables and bullets over prose - Numbers must include units - Never fabricate data points - Summary first (3 bullets max), caveats last ## Read-Before-Write Enforcement Hard rules: 1. **Never write a file you haven't read** in this session 2. **Never re-read a file** already read unless it was modified 3. **Read tests before coding** — understand what passes before writing 4. **Read error output carefully** before attempting a fix ## ASCII-Only Output Use ASCII characters only in all output: - `--` not `—` (em dash) - `"` not `"` `"` (smart quotes) - `'` not `'` `'` (curly apostrophes) - No emoji unless explicitly requested - No Unicode decorators or special characters This ensures clean copy-paste for code and compatibility with downstream systems. ## Measuring Impact Track these metrics to measure token savings: - **Output length**: average words per response (target: 30-50% reduction) - **Tool calls per task**: should stay within budget tier - **Re-read count**: should be near zero - **Write-without-read count**: should be zero - **Iteration cycles**: tests should pass in 1-2 attempts, not 5+ ## Attribution Token efficiency patterns adapted from [drona23/claude-token-efficient](https://github.com/drona23/claude-token-efficient) (MIT).
© Rohit Ghumare · MIT · rohitg00/pro-workflow
Similar skills
All skills for Agent setup: memory, context, orchestration →token-efficiency by other authors comes first.