← Back to list

dsh-quota

DeepSeek Harness Other Low risk

Bottom-right quota pill and panel aggregating membership quotas across AI platforms (Kimi Code, DeepSeek, Zhipu Coding Plan, BigModel, Qwen, Scnet, TokenRouter, SupaWriter), auto-syncing API keys from the DSH credentials domain with colored usage bars.

右下角「会员额度」悬浮球与面板,聚合各 AI 平台套餐额度(Kimi Code、DeepSeek、智谱 Coding Plan、BigModel、通义千问、超算、TokenRouter、SupaWriter),API key 自动同步自 DSH 凭证域,彩色进度条展示用量。

How to install

DeepSeek Harness dsh plugin add dsh-quota

About

dsh-quota DeepSeek Harness 插件:右下角「会员额度」悬浮球 + 面板,一眼看清各 AI 平台的套餐额度与余额。 **截图里都是什么:** **右下角的「会员额度」悬浮球**:圆点表示整体状态(绿 = 全部正常 / 黄 = 部分异常 / 红 = 全部失败),旁边是上次刷新时间;点击展开/收起面板,打开时数据超过 5 分钟会自动后台刷新 **每个平台一张卡片**:右上两个徽标——API = 官方 API 直查(key 自动同步自 DSH 凭证域,下方灰色小字显示用的是哪个凭证引用,例如 ⇄ 已同步 KIMI_CODING_API_KEY · DSH 凭证),MCP = 通过已注册的 MCP 服务器查询;正常 / 失败 / 未配 Key 是本次查询状态 **彩色进度条**:用量占比(<60% 绿 / 60–85% 黄 / >85% 红),右侧是 已用 / 上限 剩xx,下方小字是额度窗口的重置时间 **头部「刷新」按钮**:立即重新查询所有平台;面板底部「API Key 管理」折叠区可手动补 key(一般不需要——DSH 里加过的 key 会自动同步过来) 功能 **定时自动更新**:默认每 5 分钟刷新一次(refreshIntervalMinutes 可调);打开面板时数据超过 5 分钟也会自动补刷;手动「刷新」随时可用 **进度条可视化**:用量占比彩色进…

Recommendation signals

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

Meta

License
MIT
Language
TypeScript
GitHub stars
4
mo. downloads
1.9K
Last push
2026-09-24
Created
2026-08-18

Links

Basic safety check

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