Skip to content

prangishviliAbe/agent-skills / token-efficiency

token-efficiency

Verified

Make responses and agent work cheaper to read and to run without losing correctness: concise answers, TL;DR, brief status updates and final summaries, just-the-code replies, and lean tool use that avoids rereading files, dumping logs, and repeating checks. Use whenever the user asks to be brief, short, or concise, says "less text", "just the code", "TLDR", or "save tokens", complains about limits or cost, or runs a long session where context is filling up. Puts the answer first, keeps the evidence, failures, and caveats that change decisions, replies in the user's language, and never trades correctness, completeness of the work, or quality of the result for brevity.

Token and Context Efficiency

Efficiency means more useful information per word read and per token spent. It applies to how results are communicated and how work is carried out. It never applies to how well the work is done: the investigation is as thorough, the code as complete, and the design as finished as the task requires.

Output

RuleDetail
Answer firstThe first sentence is the result, the answer, or the decision needed. Background follows only if it changes what the reader does
No ceremonyNo praise of the question, restating the request, announcing what is about to be said, or closing offers and summaries of what was just said
One statement, onceDo not repeat a point in a list and again in a conclusion
Shape fits contentProse for one idea or a line of reasoning; bullets for parallel independent points; a table only for comparison across the same attributes; code blocks for anything to copy
Length fits the questionA yes-or-no question gets yes or no plus the reason. A request for depth gets depth
Show the change, not the fileLink or name the location and give the focused diff or the key lines. Full files only when asked or when the file is new and short
Keep what decidesNever cut: failures, errors, unverified parts, risks, required user actions, and numbers with units
Plain wordsFull sentences, defined terms, no private abbreviations or arrows standing in for explanations. Compressed shorthand costs the reader more than it saves
User's languageReply in the language the user writes in. Keep code, identifiers, commands, and error text exactly as they are

"Just the code" means the code and nothing else unless something would break without a note. "TL;DR" means one to three sentences, then stop.

Work

RuleDetail
Search before readingLocate with search, then read the relevant range. Do not open large files or logs whole
Read onceDo not reread a file that has not changed. Do not re-verify an edit the tool already confirmed
Batch independent callsRun unrelated reads and searches together; keep dependent steps in order
Bound outputFilter, count, or take the first and last lines of long command output; ask tools for quiet or summary modes
First causeIn a failing log, find the first error and its context; the final summary line is rarely the cause
Load only what is neededRead the reference or document section that applies to the task, not the whole set
No redundant checksRun each check for a reason; do not rerun a passing suite after an unrelated edit
Stop when doneNo speculative extra features, refactors, or files nobody asked for
Keep state compactIn long work, hold on to the objective, constraints, decisions with reasons, changed files, verified facts, and the next step; drop dead ends that no longer matter

Detail and handoff format: context-economy.md.

Progress and final messages

  • Progress updates: one line, only when something changed: a finding, a completed step, a blocker. Not a diary of commands.
  • Final message: what is now true, what was verified and how, what was not, and anything the user must do. Lead with what the reader most needs.
  • If something failed or was skipped, say so in the first lines, not buried at the end.

Examples and patterns in English and Georgian: output-craft.md.

What brevity must not remove

Never shorten awayWhy
A failing test, error, or unverified claimThe reader will assume success
The difference between ran, read, and assumed"Source reviewed; not run in a browser" must not become "tested"
A caveat that changes the decisionHidden risk costs more than a sentence
Steps the user must takeMigration, restart, key rotation, deploy
Requested scopeFinishing half the task concisely is not efficiency
Quality of the artifactDo not skip states, edge cases, or visual finish to save output
Context a cold reader needsA message read later must stand on its own

Common failures

FailureCorrect move
Three paragraphs before the answerAnswer in the first sentence
Telegraphic shorthand and undefined labelsShort, complete sentences
Everything as bullets and headersProse for reasoning; structure only where it helps
Whole file pasted for a three-line changeLocation plus the changed lines
"All tests pass" when some were not runState exactly what ran
Rereading the same file each stepKeep notes; read changed ranges only
Stopping early and offering to continueFinish the requested work
Brief reply that omits the one blockerLead with the blocker

Completion

Give the result and the least evidence needed to trust it, plus any material limit. Use Verified, Inferred, Assumed, and Not run where the distinction matters, not as labels on every sentence. Do not invent token counts, costs, or latency figures.

Skill by Abe Prangishvili — github.com/prangishviliAbe/agent-skills

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 321kUpdated Claude CodeCodexVerifiedInstall