Tokei CLI
The CLI counts code, comments and blank lines by language so an agent can describe the selected repository’s makeup.
- 15,081 ★ on the repository
- Last commit
Minimal access
Why this level
- The command reads selected source files and prints statistics without modifying them or sending them to a service.
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/tokeiDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The command reads selected source files and prints statistics without modifying them or sending them to a service.
This is third-party code. Review the repository files before installing.
What it does
Tokei reads source files and reports statistics by language. An agent can describe repository composition, compare directories and inspect per-file counts. Supported parsers distinguish code, comments and blank lines. Default output is a summary table. Builds with serialization support can emit structured formats. Users can select languages and exclude generated or third-party directories.
Who it is for. Technical assessment leads needing a language and code-volume inventory before detailed source review.
Good fit when
- Planning starts with identifying the project’s main languages.
- A monorepo needs directory-size comparisons.
- Generated files should be excluded from an inventory.
- A report needs repeatable counts over the same paths.
Not a fit when
- Line counts would replace complexity or quality assessment.
- The task needs call and dependency analysis.
- File formats are outside supported language parsing rules.
Example request
Use Tokei to count repository languages excluding vendor and generated directories, and list exclusions.Limitations
Install the package appropriate for your operating system; the first README option targets Alpine Linux. Hidden and ignored files may be omitted, so verify the included paths before comparing projects. Structured output depends on build features; unavailable formats require a matching Tokei build. Line counts describe text volume, while conclusions about engineering effort or quality require separate code analysis.
How to disable. End the command and remove it from reporting scripts. Source files are unchanged; manage saved reports separately.
FAQ
How do I get per-file counts?
Add `--files`.
Can I count several folders?
Yes. Supply their paths in one invocation.
How do I exclude a directory?
Use `--exclude` with the appropriate pattern.
Where can settings be kept?
Use `tokei.toml` or `.tokeirc` in a supported configuration location.
Why is JSON unavailable?
The build may lack serialization; inspect the program’s message and enabled features.
Discussion
No questions or reviews yet.
Related
CLI toolsA TUI that shows what Claude Code, Codex, Gemini CLI and opencode do in a project: the open file, last-commit diff, live commands
The CLI summarizes a local Git repository and its code statistics to give agents a concise starting point for project exploration.
scc counts code and comments, estimates complexity, inspects Git history and exposes analysis to agents through built-in MCP.
CLI that builds a codebase index and a 250-token map so an agent does not read hundreds of files to find the right one.
A CLI turns Git changes into a guided code walkthrough with questions and explanations written by your existing agent
A CLI that records coding-agent steps and links file lines to the tool call, conversation and original request behind them.
README in short
Summaries can be sorted by code, comments or file count. Tokei can also read previously saved statistics.