Kimi provider sourcing

Repo Signal

Last run: 74 found, 1 new

Qualified >300

100

Contact paths

89

Approved

0

Drafts

2

100Kimi/Moonshot provider builderNewJavaScript

mm7894215/TokenTracker

2 of 100

Track token usage across 15 AI agent CLIs — Claude Code, Codex, Cursor, Gemini, Kiro, OpenCode, OpenClaw, Every Code, Hermes, GitHub Copilot, Kimi Code, CodeBuddy, oh-my-pi, Kilo CLI, Kilo Code. Local-first, zero-config, with a beautiful dashboard, native macOS menu bar app, and 4 desktop widgets.

444 stars40 forksUpdated May 12, 2026Individual owner

Fit Reasons

Kimi/Moonshot provider signal: kimi

Model provider or API routing signal: api key

AI coding workflow signal: claude code, codex, cursor

Usage telemetry signal: token usage, token tracker, token-tracker

Owned by an individual GitHub user

Has enough traction to indicate active users

Outreach Draft

Hey, stumbled on TokenTracker while digging into spend tracking for Kimi Code and the other agent CLIs. Love the local first, zero config approach. I have been building around Kimi lately and was wondering how you are grabbing token counts from Kimi Code. Are you parsing stdout or did you find a cleaner hook into the CLI? Curious how that integration looks on your end.