mirror of
https://github.com/affaan-m/ECC.git
synced 2026-10-16 05:05:30 +02:00
iyashjayesh
df34108e0f
Review caught this on the previous commit, and it was right. `sync` resolves its target as `--out` if given, otherwise `.tokenchit.json`'s `output` — `tokenchit.svg` is that field's default, not a fixed location. Saying the bare command "writes tokenchit.svg in the repository root" is wrong for anyone who has configured another path. Checked rather than assumed: a config with `output: docs/custom-card.svg` makes the bare command report `would write docs/custom-card.svg`. Three places said it. Step 3 now says the configured output, the flag table no longer implies the default is fixed, and the README snippet carries a note to use the path sync actually reported. The command's usage comment says the same.
1.1 KiB
1.1 KiB
description: Render a token-usage stat card from local agent session logs and commit it to the repo. Invokes the token-card skill. argument-hint: [--out PATH] [--theme auto|light|dark] [--dry-run]
Token Card
Thin compatibility shim. The workflow lives in the token-card skill
(skills/token-card/SKILL.md), which is the canonical surface; this command exists so the
slash-command harnesses can reach it.
Usage
/token-card # write the configured output (./tokenchit.svg by default)
/token-card --out docs/usage.svg # write somewhere else
/token-card --theme dark
/token-card --dry-run # report what would be written, write nothing
What it does
Renders an SVG card of this machine's AI coding agent usage — tokens, equivalent cost, streak, per-agent split — from local Claude Code, Codex, Gemini CLI and OpenCode session logs, and writes it into the working tree as a file the README can reference.
Follow the skill for the full workflow, including the confirmation required before the first registry download, the pinned CLI version, and the dry-run rules.