Plugin directory / Knowledge / dsh-balance-tide
dsh-balance-tide
Verified · install-tested on dsh huanyuLv
What it does
DeepSeek Harness (DSH) Web plugin: balance + peak/off-peak pricing tide indicator. Shows DeepSeek account balance and current session cost, and prompts current peak/off-peak price tier, countdown to switch, and usage suggestions before balance.
Works — verified, early-stage project
DeepSeek Harness (DSH) Web plugin: balance + peak/off-peak pricing tide indicator. Shows DeepSeek account balance and current session cost, and prompts current peak/off-peak price tier, countdown to switch, and usage suggestions before balance. It installs cleanly and boots without issues in our testing. It's early-stage but functional.
“Verified” means our automated CI actually ran dsh plugin add in a clean profile and it booted — nothing more. Feature descriptions and version compatibility are the author’s claims. This is not a security audit and not an endorsement of third-party code.
README
dsh-balance-tide
English | 简体中文
DeepSeek Harness (DSH) Web plugin: account balance + peak/off-peak pricing tide indicator.
A live readout row under the composer:
[standard] peak pricing starts in 2d 5h | Balance ¥28.78 | ~¥0.42 this session | ?
Once peak/off-peak pricing takes effect (2026-08-17), the badge and countdown
follow Beijing time in real time:
[off-peak] peak in 2h 15m | Balance ¥28.78 | ~¥0.42 this session | ? ← off-peak hours
[peak] off-peak in 1h 30m | Balance ¥28.78 | ~¥0.42 this session | ? ← peak hours
Features
- Pricing badge:
standard(before 2026-08-17) /peak/off-peak, judged live in Beijing time - Countdown: time remaining until the next pricing switch, ticking every second — plan your usage ahead
- Balance: live balance from the official
/user/balanceendpoint (granted / topped-up split) - Session cost: estimated at current-period prices (reuses
sessionProjections; same-turn/step samples replace rather than double-count) - Hover details: full price tables for the current and the next period, the peak/off-peak gap (peak = off-peak × 2), peak windows, and usage advice
?icon: opens the official pricing page https://api-docs.deepseek.com/zh-cn/quick_start/pricing/- Zero config: reuses
DEEPSEEK_API_KEYfrom DSH credentials — no key in the repo, ever - i18n: UI follows the interface language (中文 / English)
Peak/off-peak schedule (Beijing time)
Per the official pricing page (2026-08 edition, last verified 2026-08-15):
- From 2026-08-17 00:00, peak/off-peak pricing applies; before that, current flat prices
- Peak windows: 09:00–12:00 and 14:00–18:00; all other hours are off-peak
- Off-peak = half of peak
| Model (per 1M tokens) | Flat (hit / miss / output) | Off-peak | Peak |
|---|---|---|---|
| deepseek-v4-flash | 0.02 / 1 / 2 | 0.05 / 1.5 / 4.5 | 0.10 / 3.0 / 9.0 |
| deepseek-v4-pro | 0.025 / 3 / 6 | 0.15 / 4.5 / 13.5 | 0.30 / 9.0 / 27.0 |
Install
From npm (recommended)
dsh plugin --profile web add dsh-balance-tide
From the Git URL
dsh plugin --profile web add https://github.com/huanyuLv/dsh-balance-tide
From a local directory
dsh plugin --profile web add file:/path/to/dsh-balance-tide
Restart dsh web to take effect. Requires pnpm (npm i -g pnpm).
Configuration (in $DSH_HOME/profiles/web/cordis.patch.yml)
- id: dsh-balance-tide
config:
refreshIntervalMs: 300000 # how often the host polls the balance API
clientPollIntervalMs: 30000 # how often the browser re-reads the cache
currency: CNY
allowedHosts: [] # register your domain here if you front dsh with a reverse proxy
When the official prices or the schedule change, override them in config — no need to
wait for a plugin release:
- id: dsh-balance-tide
config:
tideCutoff: '2026-08-17T00:00:00+08:00' # when peak/off-peak pricing starts
peakWindows: # peak hours (Beijing time, [start, end))
- { start: 9, end: 12 }
- { start: 14, end: 18 }
tidePrices: # per-tier prices (per 1M tokens)
flat:
deepseek-v4-flash: { cacheHit: 0.02, cacheMiss: 1, output: 2 }
peak:
deepseek-v4-flash: { cacheHit: 0.1, cacheMiss: 3, output: 9 }
offpeak:
deepseek-v4-flash: { cacheHit: 0.05, cacheMiss: 1.5, output: 4.5 }
peakWindows: [] means there are no peak hours at all — use it if the tiered pricing
is ever withdrawn.
Security
- Credentials: prefer
DEEPSEEK_API_KEYfrom DSH credentials. TheapiKeyconfig
option is an escape hatch only — it lands in a config file in plaintext, so avoid it.baseUrlmust be https; plaintext http is rejected outright (it would put the key on
the wire). - Balance endpoint:
/query-tideserves your account balance, so readers are checked.
The Host must be localhost, an IP literal, or a domain registered inallowedHosts
(this blocks DNS rebinding); any request carrying an Origin must be same-origin (this
blocks arbitrary web pages from reading your balance). Rejected reads get a 403. - Error reporting: the server sends only a small set of error codes to the browser;
raw exception text goes to the log, so a custombaseUrlnever leaks to the frontend.
Known limitations
- Costs are estimates computed at current-period prices; the official invoice is authoritative.
- For multi-currency accounts the readout row shows the first currency only; the rest appear in the tooltip.
deepseek-chat/deepseek-reasonerare no longer listed on the official pricing page —
the static entries inpricesare a fallback, not a verified quote.
Development
npm install
npm test
Compatibility
- DeepSeek Harness
0.1.0-rc.6+ (web profile) - Node.js 20 / 22 / 24 (covered by CI)
- Cross-platform: pure JavaScript + standard browser CSS, no native modules
- License: MIT
Install
Install the catalog once, then DeepSeek Harness can find and install any plugin from this site automatically:
dsh plugin add dshbase-catalog Then say "install dsh-balance-tide for me" — your agent finds it in the directory and installs it. Docs: dshbase-catalog · verified packs.
This plugin is GitHub source (not published to npm) — install it straight from the repo:
Web profile:
dsh plugin --profile web add github:huanyuLv/dsh-balance-tide Headless (CLI) profile:
dsh plugin --profile headless add github:huanyuLv/dsh-balance-tide Test report
Verified: L1 install + L2 load + L3 runtime from GitHub source on dsh 0.1.0-rc.6.
When to use it
Give the agent a memory, a knowledge base, or a retrieval layer so it stops forgetting context between sessions.
Who it's for
Users running long projects who want the agent to remember decisions, docs, and preferences without re-explaining.
For developers — extending it
The memory/retrieval backend is the seam — plug a new store, tune what gets distilled, or add citation and audit trails.