← Back to list

dsh-usage-panel

DeepSeek Harness Other Low risk

DeepSeek balance and per-session token usage in the session header, with a three-level balance alert and editable thresholds, one-click top-up links, a segmented token bar with cache-hit statistics, and a visibility-aware poller.

会话头部显示 DeepSeek 余额与本会话 Token 用量:三级余额预警、自定义阈值、一键充值入口、分段 Token 条与缓存命中率,并采用可见时才轮询的省流策略。

How to install

DeepSeek Harness dsh plugin add dsh-usage-panel

About

dsh-usage-panel English | **简体中文** 为 DSH(DeepSeek Harness) Web 界面提供 **DeepSeek 账户余额**与**本会话 Token 用量**,以彩色胶囊显示在会话头部右侧。 功能 **余额**:官方 GET /user/balance,显示总额 / 充值 / 赠送。 **Token 用量**:读取宿主 tokenUsage 投影,显示未缓存输入 / 缓存命中 / 缓存写入 / 输出 / 合计 / 缓存命中率。 **三级余额预警**(阈值可自定义):充足 / 警告 / 不足,胶囊与卡片颜色随之变化。 **充值入口**:去充值 / 用量明细 / 登录平台 / 复制链接;支持新标签、当前标签、复制链接三种打开方式。 **查询效率**:仅在页面可见时轮询(隐藏暂停)、失败指数退避、宿主 30s 缓存 + 单飞、手动刷新。 **跨版本兼容**:宿主端优先 ctx.connection.fetch 并回退 ctx.webServer;浏览器端依次尝试会话头部插槽。 安装 方式一:作为插件包安装(推荐) sh dsh plugin --profile web add dsh-usage-panel 方式二:本地安装脚本 sh node install.mjs --home ~/.dsh --profile web 重启 dsh we…

Recommendation signals

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

Meta

License
MIT
Language
JavaScript
GitHub stars
0
mo. downloads
670
Last push
2026-09-21
Created
2026-09-21

Links

Basic safety check

Findings
None
Sources
curated:awesome-dsh-plugin.com, curated:awesome-dsh-plugin/awesome-dsh-plugin
Topics
deepseek-harness, deepseek-harness-plugins, dsh-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 ↗