DSH Marketplace
中文

dsh-usage-stats

Ychris12138/dsh-usage-stats

Multi-provider usage dashboard with provider/model token breakdowns, calendar drill-downs, account balances, and OpenCode Go / Z.ai subscription quota tracking.

637JavaScriptMITSource

Install

Add dsh-usage-stats to DeepSeek Harness

via GitHub · GitHub source

Installing from GitHub runs the project's build script, which pnpm blocks until you allowlist it — run the command once and pnpm prints the exact key to add under `allowBuilds` in ~/.dsh/profiles/web/pnpm-workspace.yaml.

What happened when we ran it

Installed cleanly when we ran it

Every command here is run in a throwaway container against a clean profile, and the result is whatever the harness recorded — not a guess from the source. Last run 2d ago.

Due diligence

Before you install dsh-usage-stats

  • Source of record: Ychris12138/dsh-usage-stats — present in the community registry that DSH's own plugin market installs from.
  • Licensed under MIT.
  • Detected: terminal surface, requires credentials. Read the source before granting these.
  • A listing here is not a security review. Plugins run with your agent's permissions.

The AI take

What it is — dsh-usage-stats provides multi-provider account monitoring panel for DeepSeek Harness web GUI.

Who it is for — When you need to monitor token consumption and balances across multiple providers in DeepSeek Harness web, this plugin applies. If you do not wish to provide API key or token, this plugin is not suitable.

Watch out — Sandbox test passed with successful registration in a new profile. Requires providing API key or token. The plugin will execute shell commands.

The verdict — I would install it because it aggregates token usage analysis across multiple providers, but only if I have the corresponding API keys configured.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.

What dsh-usage-stats does

Abstract diagram of credentials flowing through a gateway into provider nodes, token streams, calendar tiles, and balance gauges.

dsh-usage-stats is a DeepSeek Harness plugin that monitors configured provider accounts and analyses token usage in the DeepSeek Harness web interface. DeepSeek Harness loads it in the web profile, where it adds a Usage/Balance entry and serves five loopback-only GET endpoints. The plugin reads provider profiles and credentials resolved by DeepSeek Harness from ~/.dsh/.credentials.yaml, then sends the required credentials to validated provider URLs for balance or subscription checks. It aggregates local token data by day, provider and model, while keeping keys, cookies, management PATs and upstream responses on the server.

The dashboard covers balance providers, token-plan quotas, monthly calendar drill-downs, cache-hit rates, account status thresholds and adapters including New API, Sub2API, OpenRouter, OpenCode Go, Z.ai, Kimi and MiniMax. Background refresh starts with the service and repeats every five minutes; manual refresh forces the selected account only. DeepSeek Harness plugin configuration can add monitors under the existing dsh-usage-stats entry, including restricted declarative GET queries using JSON Pointer extraction.

This is for developers who need one local view across several provider accounts and usage sources. It is a poor choice where remote account checks are unavailable or credentials must never leave the local service process: unsupported providers still yield token statistics, but no balance is inferred. The plugin also requires the DeepSeek Harness web profile and a compatible @deepseek-ai/dsh version. Its terminal surface is the Node-based installation and update path; its runtime credential and network surface exists to query configured provider endpoints.

dsh-usage-stats documentation

Configuring dsh-usage-stats

DeepSeek Harness reads credentials from ~/.dsh/.credentials.yaml; the installer does not read, create or modify this file. Provider profiles normally supply apiKeyEnv. Account-specific references include OPENROUTER_MANAGEMENT_KEY, OPENCODE_GO_API_KEY, ZAI_API_KEY, KIMI_API_KEY and MINIMAX_API_KEY. Optional region keys are ZAI_API_REGION (global by default) and MINIMAX_API_REGION (global by default). OpenRouter requires a management key, not a normal inference key.

Custom monitors are merged into the existing Cordis entry named dsh-usage-stats:

Key Purpose
monitors.<provider>.adapter Selects an adapter such as new-api, sub2api, general or declarative
warning.warnBelow / criticalBelow Absolute balance thresholds
request.path Restricted GET path for a declarative monitor
extract.* JSON Pointer locations for extracted values

Declarative monitors use credentialRef and do not execute JavaScript. Unknown provider IDs, adapters or invalid mappings stop startup before routes and timers register.

Commands for dsh-usage-stats

DeepSeek Harness manages the plugin with dsh plugin --profile web update dsh-usage-stats and dsh plugin --profile web remove dsh-usage-stats. After adding or updating the plugin, restart the running dsh web process and hard-refresh the browser. The alternative npx installer supports --dry-run, --check and --no-enable, but it is a separate installation path and must not be combined with a manual Cordis entry.

Requirements and behaviour

DeepSeek Harness requires the web profile and @deepseek-ai/dsh >= 0.1.0-rc.6. The service refreshes configured accounts and local token aggregates at startup and every five minutes, regardless of whether the panel is open. The browser requests only the selected provider. A manual refresh updates tokens and the provider list, and forces the selected account rather than all accounts.

Known limits

Providers without a public account interface can still contribute token usage, but their account card reports that balance checks are unsupported. OpenCode Go uses a non-public bearer usage endpoint that may change. Cookie credentials are equivalent to login credentials. Future timestamps are excluded, and “last 14 days” uses local calendar dates.

Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub

Same category

Alternatives to dsh-usage-stats

dsh-cost-meter

Han-1413141

70

Per-session and daily API cost, budget with usage %, official balance, history dashboard, and one-click official price sync with peak/off-peak pricing.

Installed cleanly when we ran it

GitHub sourceJavaScript2d ago

AI review

dsh-cost-meter

What it is — The dsh-cost-meter plugin integrates session cost tracking, budget monitoring, official balance display, and history dashboard into DeepSeek Harness.

Who it is for — When building multi-turn dialogue agents using DeepSeek models in DeepSeek Harness and needing to track token usage and budgets, this plugin fits. If working with other AI platforms without DeepSeek Harness integration, this plugin provides no relevant statistics.

Watch out — Sandbox testing passed: successfully installed in a new profile and registered with DSH. No obvious issues found.

The verdict — I would not install it because it only tracks API costs without affecting model behavior or outputs.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
Details

dsh-damage-pulse

wssfk12138

35

DeepSeek Harness token balance monitor with game-style damage pulse animations

Installed cleanly when we ran it

GitHub sourceTypeScriptyesterday

AI review

dsh-damage-pulse

What it is — DeepSeek Harness token balance monitor plugin with damage pulse animations on token consumption.

Who it is for — Users conducting token-intensive tasks with DeepSeek models are suitable to install this plugin. Those who only wish to check balance without needing damage pulse animations may use other tools.

Watch out — Sandbox testing passed; successfully registered in a fresh profile with normal operation. Static scan indicates the plugin will execute shell commands, but no runtime issues were found. No obvious installation or running pitfalls discovered.

The verdict — I would install it because sandbox testing passed and it provides precise token billing with cache-aware animations, but only if using the DeepSeek API and requiring real-time balance monitoring.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Source

TokenLedger

zh667

26

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.

Installed cleanly when we ran it

npm packageJavaScript2d ago

AI review

TokenLedger

What it is — TokenLedger plugin provides a sidebar usage panel for DeepSeek Harness Web GUI, attributing tokens to the relay site that served each request.

Who it is for — When you use multiple provider routes in DeepSeek Harness web profile, you need to know which relay site served each token request. If you only need to view token balance data for a single provider without usage analysis, then the plugin's statistical features are not applicable to you.

Watch out — Sandbox testing passed: installed in a new profile and registered into the profile by harness. No obvious pits found.

The verdict — If I were you, I would install it because it automatically discovers the relay site and supports balance queries for multiple providers.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Source

deepseek-harness-wallet

feibi-mochi

25

Multi-provider wallet chip: official DeepSeek balance, per-session cost & tokens, third-party token totals, recharge shortcut, low-balance alerts.

Installed cleanly when we ran it

npm packageJavaScript3d ago

AI review

deepseek-harness-wallet

What it is — A DeepSeek Harness plugin displaying official DeepSeek balance, per-session cost and token totals, with recharge shortcut and low-balance alerts.

Who it is for — When you use the DeepSeek model in DeepSeek Harness for multi-turn conversations and need to track session costs, this plugin is suitable to install. If you mainly manage third-party token totals and are not concerned with official balance, the plugin's focus does not match your needs.

Watch out — Sandbox test passed. It was installed in a new profile and registered into the profile. No obvious issues found.

The verdict — I would install it because it buckets official DeepSeek costs per provider and per session without mixing with other providers.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
Source

dsh-usage-plugin

feiyang-dev

23

DeepSeek Harness 用量与消耗插件（dsh-usage-plugin）—— 每次调用的 token 用量/缓存命中统计、峰谷计费、余额查询、CSV/JSON/PNG 导出，可经桌面端一键安装或命令行 dsh plugin add 安装。

Installed cleanly when we ran it

npm packageJavaScript3d ago

AI review

dsh-usage-plugin

What it is — dsh-usage-plugin is a DeepSeek Harness plugin that records token usage, cache hits, and costs for model calls and supports exports.

Who it is for — Users conducting multi-turn model conversations in the DeepSeek Harness web interface should install this plugin to track token usage. Users running in headless profiles do not need this plugin because headless mode does not require web UI tracking panels.

Watch out — Sandbox test passed: works normally in a new profile and is registered by harness. Supports cross-platform file path handling. No obvious issues found.

The verdict — If you need to analyze token consumption in DeepSeek Harness web interface, I would install it because it records detailed usage and exports.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Source

dsh-usage

Aisland-SJL

20

🌊 Persistent dock & fully-customizable balance/usage panel for DeepSeek Harness — activity heatmap, dual-channel comparison, local-only & privacy-first

Installed cleanly when we ran it

GitHub sourceJavaScript2d ago

AI review

dsh-usage

What it is — dsh-usage provides persistent dock and fully customizable balance/usage panel for DeepSeek Harness including activity heatmap and dual-channel comparison.

Who it is for — If sidebar collapses and you need ongoing token balance monitoring in DeepSeek Harness, this plugin is suitable as it maintains a persistent dock. Users who do not use multiple channels or require dual-channel comparison can skip it.

Watch out — Requires manually approving the build script when installing from source. Successfully tested in a new profile where it registers into the profile. No obvious issues found.

The verdict — I would not install it because the static check shows it executes shell commands and credential setup for multiple providers is needed to get full value.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Source