← Back to list

dsh-opencode-go-quota

DeepSeek Harness Other Low risk

Bottom-right 余额 badge for the DSH Web UI: on expand it fetches the currently-selected provider's OpenCode Go plan limits or DeepSeek prepaid balance, plus local token usage and pricing-based spend estimates.

DSH Web 右下角「余额」徽标:展开时读取当前所选提供方,显示 OpenCode Go 计划限额或 DeepSeek 预充值余额,并附本机 token 用量与按定价表估算的消费金额。

How to install

DeepSeek Harness dsh plugin add github:zer0zio-stack/dsh-opencode-go-quota

About

dsh-opencode-go-quota DeepSeek Harness(DSH)Web 插件:右下角常驻一枚**静态胶囊「余额」**,点击展开后 立即按**当前选择的模型提供方**拉取并显示: **plan 型提供方**(订阅制,如 OpenCode Go):显示「限额」与滚动 / 本周 / 本月限额进度。 **tokens 型提供方**(预充值余额,如 deepseek-official):显示「余额」与充值/赠送明细, 并按 DeepSeek V4 定价表估算 **今日 / 本周 / 本月消费金额**,同时显示本机 token 用量。 限额与余额直接来自提供方 API;消费金额由「会话日志中的 token 用量 × 定价表」估算, 因为 DeepSeek 官方没有消费明细接口。 胶囊不轮询、不订阅模型切换,始终只显示「余额」二字;卡片**默认折叠**, 每次展开时立即读取当前选中模型并请求一次数据,再次展开会重新请求。 任一 plan 窗口达到 rate-limited 时卡片内以红色提示「已达限额」。 截图 / Screenshots | DeepSeek 余额和用量 | OpenCode Go 限额 | | --- | --- | | | | 当前提供方如何判定 浏览器半把 useSessions 里的当前 sessionId 传给 Host,Host 按以下顺序解析…

Recommendation signals

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

Meta

License
MIT
Language
JavaScript
GitHub stars
1
mo. downloads
–
Last push
2026-08-16
Created
2026-08-15

Links

GitHub ↗ Report issue ↗

Basic safety check

Findings
curated 收录但无 npm 包/安装命令
Sources
curated:awesome-dsh-plugin.com, curated:awesome-dsh-plugin/awesome-dsh-plugin
Topics
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 ↗