Skip to content

v0.8.0 — MCP server, card-refresh Action, per-agent pages

Latest

Choose a tag to compare

@iyashjayesh iyashjayesh released this 12 Sep 07:07
· 90 commits to main since this release

The action

iyashjayesh/tokenchit@v0.8.0 refreshes the tokenchit card already committed in your repo, so the SVG in your README stops drifting away from the numbers it claims to show.

- uses: actions/checkout@v7
- uses: iyashjayesh/tokenchit@v0.8.0
  with:
    handle: your-handle

It does not read your logs, and it cannot — a runner has no access to ~/.claude or ~/.codex, so you still run tokenchit publish from the machine that has them. What the action does is re-fetch the card you already published and commit it, which keeps readers on a committed file rather than an endpoint.

It refuses to overwrite a good card with a bad response: a non-200, a body that is not an SVG, or the placeholder the endpoint returns for a handle with nothing on the board. That last one matters — without it, a typo in handle commits an empty card on a schedule, silently, forever.

Inputs: handle (required), output, layout, theme, agents, hide, commit, commit-message. Outputs changed.

Note that GitHub disables scheduled workflows after 60 days with no repository activity, and a run that finds an unchanged card makes no commit, so on a quiet repository the schedule can switch itself off. workflow_dispatch is there to start it again.

@tokenchit/mcp

A new package: an MCP server exposing your local agent usage, so a model can answer questions about it instead of you reading a table.

{ "mcpServers": { "tokenchit": { "command": "npx", "args": ["-y", "@tokenchit/mcp@latest"] } } }

Four tools — get_usage, get_daily_usage, get_recap, detect_agents — reading the same logs through the same aggregation as the CLI, so the figures cannot drift from the card. None of them can make a network request: net.isolated covers packages/mcp/src and the package has no allowlisted network module at all.

The site

Pages per agent at /tool/claude-code, /tool/codex and /tool/opencode, each carrying the caveat specific to that adapter. The landing page now states that the tool is free, ends with the install command instead of a heatmap, and no longer leads its headline figures with an equivalent-cost number the page spends three paragraphs qualifying.

CLI

publish now closes with the embed snippet and the git add line. It previously ended on two links to a website, for a tool whose argument is that the card belongs in your repo.