workflowstacks
analytics

Token-Monitor: Track AI Costs

Get real-time token and cost insights with Token-Monitor, a multi-device sync widget for AI tools, designed for founders using Claude Code, Codex, and more.
1,599 stars144 forksJavaScriptHealth Score 9/10Updated 8/22/2026100% free · open source
What it does

Token-Monitor provides real-time insights into token and cost usage for AI tools like Claude Code and Codex, with multi-device sync capabilities.

Install / run
git clone https://github.com/Javis603/token-monitor.git && cd token-monitor
When to use it
  • When you need to track and manage AI token usage across multiple devices and team members
  • When you want to monitor and limit AI costs in real-time to avoid unexpected expenses
  • When you are using multiple AI tools and need a unified dashboard to monitor token and cost usage
Quick start
  1. 1Run `npm install` to install required dependencies
  2. 2Configure your AI tool credentials in the `config.json` file
  3. 3Start the Token-Monitor server with `npm start`
  4. 4Access the Token-Monitor dashboard at `http://localhost:3000`
  5. 5Configure multi-device sync by following the instructions in the `README.md` file
Ready-to-paste prompt
Open `config.json` and add your Claude Code API key: `{ "claudeCode": { "apiKey": "YOUR_API_KEY_HERE" } }`
Heads up: Make sure you have Node.js (version 16 or higher) installed on your system, as Token-Monitor requires it to run
Saves to your device

Topics

ai
ai-tools
antigravity
claude-code
codex
cursor
deepseek
deepseek-harness
dsh
hermes-agent
linux
llm
local-first
macos
openclaw
opencode
self-hosted
token-tracker
token-usage
windows
How Token-Monitor: Track AI Costs works
Codeflow
Free to inspect

Token-Monitor: Track AI Costs is a very large JavaScript project (~78k lines across 257 code files, plus 286 test files). It is a full software project: use it through its install path rather than reading it end to end. Last commit this month, MIT license, has a test suite.

Size
Very large codebase
~78k lines · 257 code files · days to read — use, don't read
Setup
Developer setup
A real software project. Use it via its install path; don't expect to read it all.
Runs on
Node.js
Needs API keys (.env)
JavaScript 91%CSS 4%HTML 2%Swift 2%
Where to start reading
  1. 1
    README.md
    Start here — what it does and how to install it
  2. 2
    AGENTS.md
    The instructions the AI actually follows
  3. 3
    package.json
    Dependencies and the commands it exposes
  4. 4
    .env.example
    The API keys and settings you must provide
  5. 5
    src/electron/main.js
    Inside src/ — the main logic begins here
What's in each folder
src/Core code — the actual logic233 files
site/Frontend / UI59 files
worker/Backend / API22 files
docs/Documentation9 files
scripts/Helper scripts24 files
native/Folder15 files
tests/Tests — proof it works289 files
.github/CI / automation (GitHub Actions)62 files
READMEHas testsDocumentedCI checksMIT licenseUpdated this month
Quick Actions
Details
Creator
Javis603
Language
JavaScript
Category
analytics
Published
5/19/2026

Are you the creator of this tool? Claim your listing → and earn 85% of every sale.