SkillAgentSearch skills...

token-efficiency

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.

Install / Use

npx skills add rohitg00/pro-workflow --skill token-efficiency

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Supported Platforms

Claude Code

Tags

Our assessment of token-efficiency

token-efficiency scores 83/100 on our quality scale, 3088th of 4,698 Development & Engineering skills we index.

Its SKILL.md is 4.0 KB long, well organised into 13 sections and no code examples: a solid amount of guidance for an agent.

With 2,876 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
13/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so token-efficiency is actively maintained.
  • Our last check on 2026-11-07 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

token-efficiency compared with similar skills

All 4 of these similar skills score higher than token-efficiency; compare them before choosing.

SkillScoreStarsUpdatedFormat
token-efficiency (this skill)by rohitg00832.9k53d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install token-efficiency?
Run npx skills add rohitg00/pro-workflow --skill token-efficiency. The install tabs above show the steps for each supported agent.
Which AI agents does token-efficiency work with?
It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
Is token-efficiency safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is token-efficiency still maintained?
The repository was last updated about 2 months ago, so token-efficiency is actively maintained.

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 (MIT).

Related Skills

View on GitHub
GitHub Stars2.9k
CategoryDevelopment
Updated1mo ago
Forks289

Languages

JavaScript

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium