token-stats

Analyze and visualize token economics comparing search-first methods to blind file reading.

6|1|Updated Feb 6, 2026

Search Tags:#search #efficiency #code exploration #cost savings #Claude API #token economics

Ready to run

npx skills add https://github.com/mahmoudimus/simba --skill token-stats-mahmoudimus

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: token-stats
Source: https://github.com/mahmoudimus/simba/tree/main/skills/token-stats
Command: npx skills add https://github.com/mahmoudimus/simba --skill token-stats-mahmoudimus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps users understand and quantify the token savings achieved by using a search-first approach to code exploration compared to blind file reading.

Core Features & Use Cases

Token Usage Analysis: Compares estimated token costs for different exploration strategies.
Codebase Size Metrics: Displays total files, lines, and estimated tokens in the project.
Session Activity Log: Tracks files read, edited, and searches performed during a session.
Use Case: Developers can see tangible proof of how using the simba plugin reduces Claude API costs and improves efficiency.

Quick Start

Run the token-stats skill to see a dashboard of your current session's token economics.

Frequently Asked Questions about token-stats

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

FAQPage Schema

How do I calculate token savings when exploring code with the Claude API?▼

You can calculate token savings by analyzing session activity logs that compare search-first exploration against blind file reading, providing exact metrics on token costs avoided during your specific development workflow.

What is the best way to track token economics for AI-assisted development workflows?▼

Tracking token economics involves visualizing session-specific activity logs that record files read, edited, and searches performed, allowing developers to see tangible proof of API cost optimization and efficiency.

How do I measure codebase size metrics for token cost optimization?▼

Measuring codebase size metrics involves displaying total files, lines, and estimated tokens in the project, which helps quantify potential token costs and understand the scale of your codebase for cost savings.

Does a search-first approach to code exploration actually reduce Claude API costs?▼

A search-first approach reduces Claude API costs by avoiding blind file reading, and this Skill visualizes the actual token savings achieved by comparing estimated token costs between different exploration strategies.

Can I visualize historical token memory usage data for past coding sessions?▼

You can visualize historical memory usage data alongside session-specific activity logs, which track files read, edited, and searches performed to show long-term token economics and cost savings trends.

What are the limitations of analyzing token economics without blind file reading comparisons?▼

Without comparing search-first methods against blind file reading, the token savings analysis lacks a baseline, making it difficult to accurately quantify the actual cost optimization and efficiency improvements achieved.