token-stats

Quantifies token usage and savings from search-first codebase exploration via activity logs.

15|1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/iagocavalcante/claude-turbo-search --skill token-stats
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: token-stats
Source: https://github.com/iagocavalcante/claude-turbo-search/tree/main/skills/token-stats
Command: npx skills add https://github.com/iagocavalcante/claude-turbo-search --skill token-stats

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Token economics for codebase exploration is often opaque, making it hard to quantify savings from search-first strategies.

Core Features & Use Cases

  • Token savings visualization: shows how search-first reduces total tokens compared to blind reads.
  • Session analytics: aggregates activity like searches, reads, and edits to inform optimization decisions.
  • Codebase assessment: estimates total tokens across a project and highlights optimization opportunities.

Quick Start

Invoke /token-stats to display the current session's token economics dashboard.

Frequently Asked Questions about token-stats

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track token usage and savings when exploring a codebase?

You can track token usage and savings by calculating searches, reads, and token estimates from activity logs to quantify the cost implications of codebase exploration sessions.

What is search-first codebase exploration and how does it reduce token cost?

Search-first codebase exploration reduces total tokens by performing targeted searches instead of blind reads, minimizing memory usage and lowering the overall token cost of navigating large projects.

How do I visualize token economics for a coding session?

You can visualize token economics by generating a deterministic dashboard that aggregates session activity like searches and reads to display token savings and inform optimization decisions.

Can I compare token efficiency across different codebases and projects?

Yes, you can compare token efficiency across projects by applying token estimation to activity logs from different codebases, highlighting optimization opportunities and cost differences between sessions.

Does this token analytics tool require any external dependencies or components?

No, this token analytics tool operates without external dependencies or components, calculating token estimates directly from activity logs to produce a savings dashboard.

What's the best way to assess total tokens across a project for optimization?

The best way to assess total tokens is to estimate token usage across the project from activity logs, which highlights optimization opportunities and quantifies savings from search-first strategies.