dsh-token-meter-panel
Adds a sidebar panel to the DeepSeek Harness web UI that reports token usage and cost straight from DeepSeek's own usage API (today's spend, 7/30-day trends, today's hourly split, a history table, cost breakdown, peak/off-peak tier pricing), plus per-session detail from local logs. Zero-config: it reads the browser sign-in for the official figures, and falls back to local session logs with the source labelled.
在 DeepSeek Harness 侧栏加入 Token 用量与花费面板：直接采用 DeepSeek 官方用量接口（今日消费、7/30 天趋势、今日分时、历史表、成本构成、峰谷分档计价），并用本机会话日志给出按会话明细。凭据零配置——自动读取浏览器登录态取官方数据，取不到时退回本地日志并标明来源。
How to install
dsh plugin add dsh-token-meter-panel About
dsh-token-meter-panel DSH（DeepSeek Harness）的 Token 用量与花费面板插件。 在侧栏加一个独立视图：今天花了多少钱、花在哪、缓存帮你省了多少。 English | 中文 --- **本插件是社区插件，并非 DeepSeek 官方插件。** 与深度求索（DeepSeek）无隶属、合作或背书关系。 项目名使用官方品牌规范建议的缩写 **DSH**；"DeepSeek"、"DeepSeek Harness" 是深度求索公司的商标。 > **面板里的金额是本机估算，不是官方账单。** 内置费率核对自 DeepSeek 官方定价页（采集日期见下文）， 价格可能随时变动，**请以官方页面为准**；本插件不作任何计费承诺。 --- 它解决什么问题 DSH 会把每次模型调用的 token 用量记在会话日志里，但**只记 token，不算钱**——内核里没有任何计价代码。 这个插件把用量翻译成你真正关心的东西： **今天花了多少**（人民币），还剩多少预算 **钱花在哪**：缓存命中输入 / 未命中输入 / 输出 三类各占多少 **缓存省了多少**：DeepSeek 的缓存命中价只有未命中的 1/50，这个数字通常很大 **哪个会话在烧钱**：按会话列明细，子代理会话单独打标 **什么时候在烧**：今日 24 小时分布，标出峰值 --- 功能 | 区块 …
Recommendation signals
Meta
- License
- MIT
- Language
- JavaScript
- GitHub stars
- 0
- mo. downloads
- –
- Last push
- 2026-09-24
- Created
- 2026-09-20
Basic safety check
- Findings
- None
- Sources
- curated:awesome-dsh-plugin.com, curated:awesome-dsh-plugin/awesome-dsh-plugin
- Topics
- cost-tracking, deepseek-harness, dsh, dsh-plugin, token-usage
Related plugins
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.
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.
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.
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.