← Back to list

dsh-balance-tasks

DeepSeek Harness Other Low risk

Floating card showing DeepSeek balance, peak/off-peak tier countdown, and remaining tasks estimated from historical per-task token usage and the current context.

右下角悬浮卡显示 DeepSeek 余额与峰谷档位倒计时,并基于历史平均单任务 Token 消耗与当前上下文估算剩余任务数。

How to install

DeepSeek Harness dsh plugin add github:Bil812/dsh-balance-tasks

About

dsh-balance-tasks DeepSeek Harness 插件:**余额与任务数换算显示**。 右下角悬浮卡实时显示: **余额**(官方 /user/balance,总余额/赠送/充值) **还能跑多少个任务**(估算:1 任务 ≈ 1 会话;**统一口径**:每个任务价格 = 平均单次任务消耗的 Tokens(新增上下文 delta + 输出 outAvg,历史平均)× 当前档单价 + 当前已有的上下文 Tokens(按缓存命中价重读),从当前上下文起逐任务计价直到余额耗尽) **当前峰谷档位 + 距切换倒计时**(UTC 峰时段 01:00–04:00、06:00–10:00,即北京时间 9–12、14–18) 点击卡片可立即刷新余额。 安装 sh dsh plugin --profile web add <本目录> 或直接从 GitHub 安装: sh dsh plugin --profile web add github:Bil812/dsh-balance-tasks 重启 dsh web 后生效。要求已在 **设置 → 模型** 配置 DEEPSEEK_API_KEY(插件复用同一把 Key,通过凭据服务解析,不出本机)。 数据口径 usage 折叠自 llm/stream 的 usage 块(含子代理、压缩、标题等辅助调用),与官方账单口径一致; 计费价…

Recommendation signals

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

Meta

License
MIT
Language
JavaScript
GitHub stars
0
mo. downloads
–
Last push
2026-08-22
Created
2026-08-18

Links

GitHub ↗ Report issue ↗

Basic safety check

Findings
curated 收录但无 npm 包/安装命令
Sources
curated:awesome-dsh-plugin.com, curated:awesome-dsh-plugin/awesome-dsh-plugin
Topics
balance, cost, deepseek, deepseek-harness, dsh, dsh-plugin, estimate, quota

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 ↗