← Back to list

dsh-cost-balance

DeepSeek Harness Other Low risk

Collapsible iOS-style stats pill under the composer: session cost, DeepSeek account balance, cache-hit rate, and token usage in a frosted panel.

输入框下方的 iOS 风格统计条:一键展开查看会话花费、DeepSeek 账户余额、缓存命中率与 Token 用量。

How to install

DeepSeek Harness dsh plugin add dsh-cost-balance

About

dsh-cost-balance DeepSeek Harness(DSH)Web UI 插件:在输入框下方显示一条 iOS 风格的小黑条,点击展开轻盈的半透明多行面板,查看**会话花费、账户余额、缓存命中、Token 用量**等统计。 默认折叠为一条居中的小黑条(类似 iOS 底部横条),点击展开毛玻璃面板: | 行 | 内容 | |---|---| | 轮次 · 步数 | 3 轮 · 12 步 | | LLM 耗时 / 工具调用 | 45.2s / 12.3s | | 首 token 平均 / 吞吐 | 1.4s / 25.4 tok/s | | 缓存命中 | 87% | | Token | 输入 12.2K · 输出 517 | | 花费 | $0.0123(本会话,按官方定价) | | 余额 | ¥9.00(DeepSeek 账户实时余额,60s 自动刷新) | 安装(npm 发布版) sh dsh plugin --profile web add dsh-cost-balance 该命令从 npm registry 拉取已发布的 dsh-cost-balance(dsh.bundle),自动加入 profile 的 bundle 层。 然后重启(或刷新)DSH Web UI。卸载:dsh plugin --profile web remove dsh-cost-balan…

Recommendation signals

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

Meta

License
MIT
Language
JavaScript
GitHub stars
2
mo. downloads
213
Last push
2026-08-14
Created
2026-08-14

Links

GitHub ↗ npm ↗ Report issue ↗

Basic safety check

Findings
None
Sources
curated:awesome-dsh-plugin.com, curated:awesome-dsh-plugin/awesome-dsh-plugin
Topics
deepseek-harness, dsh, dsh-plugin, plugin

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 ↗