Real-time DeepSeek account balance badge in the sidebar footer with odometer roll animation, multi-currency support, balance trend chart, per-key usage statistics with historical backfill, and GitHub version auto-check.
- GitHub stars
- 4
- Version
- v1.5.0
- License
- MIT
- Added
- 2026-08-19
GitHub info
- GitHub stars
- 4
- License
- MIT
- Primary language
- JavaScript
- Last push
- Aug 19, 2026, 8:52 AM
- Maintainer
- yoiizesdev-crypto
- Added
- 2026-08-19
Install
dsh plugin --profile web add github:yoiizesdev-crypto/DSH-Balance-displayTags
README badge
Add this Markdown to your plugin README to link back to its listing.
[](https://dshget.com/plugins/yoiizesdev-crypto/DSH-Balance-display)Related plugins
Usage & Billingdsh-context
★ 1176DSH context insight panel: Context dashboard + /context command + Context browser — one-stop context lifecycle management with categorized composition, content details, evolution trends, compaction/injection events, and stats.
dsh-personal-center
★ 25Personal center for DeepSeek Harness: cross-session usage statistics, per-model cost estimation, global custom instructions, a data-driven desktop pet, and a conversation status overview, all local and offline.
dsh-all-usage
★ 4Analyze usage across models, providers, workspaces, and time ranges — including custom start/end dates over the full retained history — with live cache-hit visibility and separate model and provider breakdowns. Includes hourly single-day trends, daily cross-day trends, a 53-week GitHub-style heatmap, usage streaks, model and workspace Token-share donut charts, independent combinable filters, cache-efficiency trends, DeepSeek account balance, workspace aliases, CSV export, and a durable ledger that preserves successfully flushed usage after session deletion and rebuilds incrementally — on restart, unchanged sessions are applied from the ledger without re-reading their logs (a per-session log revision is the change signal), and only changed/new events are folded. After a scan, lightweight revision status fetches full history only when the Host/data state changes and exposes non-sensitive sync health (revision reuse, rereads, ledger recovery, and failures). Token accounting is explicit: input is fresh (cache read/write and reasoning are separate buckets) and zero-usage replays never overwrite recorded usage. Chinese uses local time, English uses UTC; API access is loopback-only.