← Back to list

dsh-balance-monitor

DeepSeek Harness Other Low risk

Shows selectable DeepSeek, Kimi, Zhipu GLM, and TeamoRouter balances in the DSH Web sidebar, with per-provider details, usage data, and refresh controls.

在 DSH Web 侧边栏展示可选的 DeepSeek、Kimi、智谱 GLM 和 TeamoRouter 余额,并提供渠道详情、用量数据与刷新控制。

How to install

DeepSeek Harness dsh plugin add @shawnkung/dsh-balance-monitor

About

dsh-balance-monitor 界面预览 侧边栏展示选定渠道的余额;点击入口可查看各渠道详情,并在设置中调整展示、精度与凭据来源。 侧边栏余额 余额详情 插件设置 功能 在“新会话”和工作区之间展示所选渠道的余额,不干扰任务看板等其他侧边栏插件。 点击侧边栏入口后,弹窗按用户设置的顺序展示已配置 API Key 的渠道,以及支持渠道的消费、请求数和 Token 用量;未配置渠道不会显示。 支持单渠道刷新与全量刷新,并通过颜色渐变反馈刷新结果。 会话结束后,根据当前模型 Provider 的实际 API 域名或受支持的内置 Provider ID,定向刷新对应渠道。 支持浅色、深色和跟随系统主题。 在插件设置中选择侧边栏展示渠道、配置凭据引用和 TeamoRouter 查询范围。 启动时检查 npm 新版本,并可在插件内完成精确版本更新。 支持渠道 | 渠道 | 余额 | 每日/区间消费 | Token 用量 | 自动刷新识别 | | --- | --- | --- | --- | --- | | DeepSeek 官方 API | 是 | 否 | 否 | deepseek.com、deepseek-official、deepseek | | Kimi 官方 API | 是 | 否 | 否 | moonshot.cn、moonshotai-cn | | 智谱 GLM | 是 …

Recommendation signals

58 Tool quality · Based on stars, downloads, maintenance, security and docs
– User interest · Adjusted by in-site views, install copies and download clicks
58 Overall
0views
0unique visitors
0install copies
0download clicks
0outbound clicks

Meta

License
MIT
Language
JavaScript
GitHub stars
0
mo. downloads
2.0K
Last push
2026-09-14
Created
2026-09-08

Links

Basic safety check

Findings
None
Sources
curated:awesome-dsh-plugin.com, curated:awesome-dsh-plugin/awesome-dsh-plugin
Topics
balance-monitor, deepseek, dsh, dsh-plugin, teamorouter, usage-monitor

Related plugins

DeepSeek Harness
Score73

TokenLedger

zh667/TokenLedger

Sidebar usage panel that attributes tokens to the relay site that served each request, read from your existing provider config: today/month/all-time totals, per-site and per-model breakdowns, a year activity heatmap, and New API / Sub2API / DeepSeek balances.

☆ 202 ↓ 1.4K Other ↗
DeepSeek Harness
Score71

dsh-context

bowenliang123/dsh-context

DSH 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.

☆ 1.5K ↓ 79.7K Other ↗
DeepSeek Harness
Score69

dsh-usage-statistics-panel

HaoyueQin/dsh-usage-statistics-panel

Usage statistics settings panel: 26-week activity heatmap, daily token trend with a cache hit-rate curve, per-model donut and breakdown, time-range filters, summary cards, one-time historical backfill and lossless rebuild.

☆ 9 ↓ 3.3K Other ↗
DeepSeek Harness
Score68

dsh-all-usage

ParticleLight/dsh-all-usage

Analyze 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 with Token, cost, and percentage details, 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 after a workspace is deleted, where its recorded usage is summed into one Deleted row — 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. The workspace registry is kept fresh automatically through the DSH domain/changed probe: only added/removed workspaces are reprocessed incrementally, unchanged workspaces reuse their computed aggregates and ledger with zero rescan, and usage is strictly limited to DSH-registered workspaces (unregistered cwds are ignored). 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.

☆ 8 ↓ 2.8K Other ↗