← Back to list

dsh-token-plan-quota

DeepSeek Harness Other Low risk

Balance badge that follows the active model provider: official readings for DeepSeek, Qwen Token Plan and Aliyun BSS, plus Moonshot and OpenRouter endpoints not yet key-verified.

跟随当前模型供应商的额度徽标:DeepSeek、千问 Token Plan、阿里云费用中心取官方真值,Moonshot / OpenRouter 已接官方端点但字段未用真 Key 核对;其余只报本实例实测。

How to install

DeepSeek Harness dsh plugin add dsh-token-plan-quota

About

dsh-token-plan-quota 中文 | English 在 DeepSeek Harness 网页界面的输入框工具行里显示**额度**: 官方接口给真值,没有官方接口的供应商显示明确标注「实测」的本实例消耗——**零配置**,装完按你实际在用的 供应商路由自动决定该开哪些源。 输入框工具行里的徽标是个小胶囊,跟随当前模型的供应商切换(名字/速度/天数都在 tooltip 里): ▓▓ 75% 官方给了分母 → 画条、报百分比 123.5万 tok 实测 没有官方分母 → 只报用了多少,绝不画条、绝不报百分比 **① 徽标跟随当前模型的供应商切换**——这一家官方接口给真值,切到没有官方额度接口的那家就退回「实测」: **② 明细面板**:官方余量卡(有官方分母才画条、才给百分比)+ 一张卡里的多窗口计量条: **③ 面板可以拖成悬浮小窗**(拖标题栏,双击复位): **④ Cookie 掉线时退回「实测」卡**:官方卡变成一张写清原因的**错误卡、不带任何数字**,兜底的实测卡留在徽标上—— 没有官方分母就不画条、不报百分比: **⑤ 按钱计费的模型也认得**:DeepSeek 的余额是官方真值,但它没有"总量"这个分母 ⇒ 不画条、不报百分比, 只把「还剩多少钱、充过多少、赠过多少」原样报出来: **⑥ 用过的模型会显示额度**:官方接口真给了分母的,才画余量条、才报…

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
1
mo. downloads
190
Last push
2026-09-23
Created
2026-09-06

Links

Basic safety check

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

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 ↗