What is token-efficiency?

A coordination approach for reducing repeated language-model work while several agents collaborate. It uses shared context, caching, grouped operations, and session measurements.

Use it when coordinating complex searches or multi-agent tasks, especially when you want to cache results, batch related operations, and review token usage afterward.

Agents can waste tokens by rereading files, repeating searches, or receiving duplicated context. This approach helps reuse information while keeping track of the savings.

token-efficiency — Command for Claude Code by f-amine/vibe-stack

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/f-amine/vibe-stack

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/f-amine/vibe-stack/token-efficiency/github.svg)](https://agentmods.dev/commands/f-amine/vibe-stack/token-efficiency)

Your own site

<a href="https://agentmods.dev/commands/f-amine/vibe-stack/token-efficiency"><img src="https://agentmods.dev/badge/commands/f-amine/vibe-stack/token-efficiency/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/f-amine/vibe-stack/token-efficiency"><img src="https://agentmods.dev/badge/commands/f-amine/vibe-stack/token-efficiency.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 247 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00247
Opus 5.5	$0.00000	$0.00099
Sonnet 5.5	$0.00000	$0.00049
Haiku 4.5	$0.00000	$0.00025

Measured 1mo ago against content hash ecb6c03b491c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

token-efficiency scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to token-efficiency — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/analysis/token-efficiency.md · 45 lines

What it actually says

Token Usage Optimization

Purpose

Reduce token consumption while maintaining quality through intelligent coordination.

Optimization Strategies

1. Smart Caching

Search results cached for 5 minutes
File content cached during session
Pattern recognition reduces redundant searches

2. Efficient Coordination

Agents share context automatically
Avoid duplicate file reads
Batch related operations

3. Measurement & Tracking

# Check token savings after session
Tool: mcp__claude-flow__token_usage
Parameters: {"operation": "session", "timeframe": "24h"}

# Result shows:
{
  "metrics": {
    "tokensSaved": 15420,
    "operations": 45,
    "efficiency": "343 tokens/operation"
  }
}

Best Practices

Use Task tool for complex searches
Enable caching in pre-search hooks
Batch operations when possible
Review session summaries for insights

Token Reduction Results

📉 32.3% average token reduction
🎯 More focused operations
🔄 Intelligent result reuse
📊 Cumulative improvements

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 45 lines · 0 tokens per session scan A ecb6c03b491c

Subscribe to this mod's changes

token-efficiency is a command published in the GitHub repository f-amine/vibe-stack (21 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 247 tokens. A static security scan graded it A with 0 findings. It is 100% identical to token-efficiency, differing in 0 lines, and is treated as a copy.

Building agents Claude Code ai better-auth claude drizzle-orm nextjs

token-efficiency