← Back to list

dsh-deepseek-monitor

DeepSeek Harness Other Low risk

Official DeepSeek platform monitoring inside the provider card: a live balance chip left of the composer model name plus an expandable account-details panel with per-model monthly usage and a daily stacked chart.

在官方供应商卡片内实时监控 DeepSeek 余额与开放平台用量——输入框工具行模型名称左侧的余额 chip,可展开的账户明细面板含按模型用量与每日堆叠图表。

How to install

DeepSeek Harness dsh plugin add dsh-deepseek-monitor

About

DSH DeepSeek Monitor English | 简体中文 DeepSeek Harness(dsh)Web 插件:把 DeepSeekMonitorWindows 的**余额与用量监控**能力移植进 dsh —— 集成到「设置 → 模型 → DeepSeek」供应商卡片内,并在输入框工具行(模型名称左侧)显示实时余额。 截图:设置 → 模型 → DeepSeek 卡片展开的「账户明细」面板(余额卡 / 模型用量行 / 每日堆叠柱状图),以及名称旁的余额 chip 与「账户明细」按钮。 功能特性 设置 · 模型 · DeepSeek 行内增强 **「账户明细」按钮**:位于「编辑」左侧,克隆宿主按钮样式,视觉完全一致 **余额 chip**:模型名称旁实时显示余额(按币种渲染符号,如 ¥/$),低于阈值变红 **展开面板**(点击按钮在卡片容器内展开): **账户余额**:官方 GET /user/balance API,复用 dsh 已配置的密钥;今日消耗 / 本月费用 mini 格(按账户币种渲染,无余额快照时回退 ¥);低余额警示 **模型用量行**:固定顺序 Flash → Vision → Pro,平台全称显示、lucide SVG 图标(闪电 / 照片 / 大脑)、独立柔和配色(天蓝 / 雾紫 / 品牌蓝)、进度条 + 缓存命中率 + 费用,行高恒定 **每…

Recommendation signals

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

Meta

License
MIT
Language
TypeScript
GitHub stars
2
mo. downloads
1.3K
Last push
2026-09-17
Created
2026-08-22

Links

Basic safety check

Findings
None
Sources
curated:awesome-dsh-plugin.com, curated:awesome-dsh-plugin/awesome-dsh-plugin
Topics
balance-monitor, deepseek, deepseek-api, deepseek-harness, dsh, dsh-plugin, mit-license, monitor, react, typescript, usage-monitoring, web-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 ↗