Both agents get the same skill-first flow. The skill calls the local runtime, reads the structured analysis, and then lets Codex or Claude Code write the final response using the session you are already in, instead of a separate API key.
Or be specific
/token-receipt Generate a receipt for my last 30 days of Codex, Claude Code, Kiro CLI, and Cursor usage.
Token Receipt is a screenshot-first usage artifact for coding agents.
It reads the session logs that Codex, Claude Code, and Kiro CLI already write locally, plus experimental local Cursor workspace metadata and request traces, turns those into structured usage facts, and lays them out as an itemized bill.
The result feels personal because it reflects your own habits: repeated file reads, subagent sprawl, context bloat, and every other expensive little ritual.
Kiro CLI is supported as a local session source. Token Receipt reads the Kiro SQLite session store, extracts tool activity and local credit usage, and folds that into the same receipt flow as the other supported agents.
Because Kiro does not expose the same local token counters here, the Kiro portion of the bill uses local credit usage instead of a token-derived API estimate.
Cursor is supported experimentally from local workspace metadata and request trace logs. That gives Token Receipt enough signal to group Composer activity, count reads and searches, and fold those habits into the same receipt flow.
The tradeoff is accounting fidelity. Cursor does not currently expose the same local token and cost counters here, so the receipt treats Cursor as behavior-rich but spend-light.
The accurate observability product is not the point.
The point is a screenshot people instantly understand: your coding agent bill, officially itemized, with a line item for every bad habit you already know you have.
Real local signals make the output feel specific instead of generic.
V1 focuses on signals we can defend from the logs:
Context window emotional support
Repeated file reads
Repeated shell confidence loops
MCP tool tourism
Subagent middle management
Planning before touching a file
Cache-heavy sessions
Low-output expensive runs
Every bill is derived from local agent logs.
Token Receipt is local parsing plus agent-native copywriting, not a new hosted AI layer.
1.
The runtime scans local Codex, Claude Code, and Kiro CLI session logs, plus experimental Cursor local artifacts
2.
Deterministic heuristics turn those logs into receipt facts
3.
The skill asks Codex or Claude Code to phrase the final response using the session you are already paying for
No prompt uploads by default. No telemetry in v1.
MIT licensed and open source.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。