From core
Guides token-efficient tool patterns: Edit for diffs, Glob/Grep for searches, concise context. Applies always to extend session capacity.
How this skill is triggered — by the user, by Claude, or both
Slash command
/core:token-efficiencyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
han-core:token-efficiency
han-core:token-efficiency
Minimize token consumption without sacrificing quality. Every token spent on overhead is a token not available for thinking.
| Wasteful | Efficient |
|---|---|
| Read file → Write entire file with 1 line changed | Edit the specific line |
cat file.txt via Bash | Read tool |
find . -name "*.ts" via Bash | Glob **/*.ts |
| "Let me start by reading the file to understand..." | Just read it |
Always. Token efficiency is not premature optimization — it directly extends how much work fits in a session.
npx claudepluginhub thebushidocollective/han --plugin coreApplies token optimization rules to reduce context usage and response length. Always active, it minimizes file reads, avoids preamble, and batches tool calls.
Minimizes token waste in bash, file reads, and data processing using jq for JSON, yq for YAML/TOML, awk for CSV, and ast-grep for precise searches.
Reduces token waste through anti-sycophancy rules, tool-call budgets per task type, one-pass coding discipline, and read-before-write enforcement.