Skill Detail

Watch local agent token usage and session traces with TokenTelemetry

Use TokenTelemetry to read local Claude Code, Codex, Gemini CLI, Hermes, and other agent logs into a dashboard for token usage, costs, tool calls, project activity, budgets, and session traces.

Monitoring & AlertsMulti-Framework
Monitoring & Alerts Multi-Framework Published
⭐ 368 GitHub stars ⬇ 347/wk npm
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill watch-local-agent-token-usage-and-session-traces-with-tokentelemetry Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
TokenTelemetry, Python 3.9 or newer, supported local agent logs such as Claude Code, Codex, Gemini CLI, Cursor, OpenCode, Hermes Agent, or similar.
Install & setup
Install with curl -fsSL https://tokentelemetry.com/install.sh | bash on macOS or Linux, irm https://tokentelemetry.com/install.ps1 | iex on Windows PowerShell, or clone https://github.com/VasiHemanth/tokentelemetry and follow the README. Run it on the same host as the agent logs so it can auto-detect sessions locally.
Author
Vasi Hemanth
Publisher
Independent
Last updated
Sep 23, 2026
Quick brief

Use TokenTelemetry when an operator runs multiple coding or autonomous agents and needs a local dashboard for token burn, session traces, tool calls, model efficiency, project activity, budget alerts, and plan-limit visibility. TokenTelemetry reads the log files agents already write, binds locally by default, and supports Codex, Claude Code, Gemini CLI, Cursor, Hermes Agent, and other agent surfaces without requiring application instrumentation.

How it works

What this skill actually does

The repeatable workflow is concrete: install TokenTelemetry, run it on the same machine or host where agent logs live, let it auto-detect supported agents, review token and cost dashboards, inspect waterfall traces, compare projects or models, and configure observational budgets or remote access only when needed. Invoke it instead of normal provider dashboards when the question is cross-agent, project-local, or trace-level usage analysis from files already on the machine. The scope boundary is local observability for existing agent logs, not blocking agent execution, proxying model calls, or replacing full application observability platforms.