Usage & Billing

What it is — dsh-context provides a context insight panel, /context command, and context browser for managing context composition, evolution trends, and events.

Who it is for — Users analyzing context composition and evolution in DeepSeek Harness sessions can use this plugin. Those preferring a simple chat interface without extra insights do not need it.

Watch out — Sandbox testing passed with no obvious issues. Token statistics align with official token-meter projections.

The verdict — You will install it because it offers detailed tracking of context events, which is valuable when your sessions include tool calls.

What it is — DeepSeek Harness session and daily API cost tracking plugin, displaying official balance, budget usage %, and history dashboard.

Who it is for — When using DeepSeek Harness for session tasks that require monitoring official balance and budget usage percentage, it fits. Users not using official price can choose not to install it, because it emphasizes official price synchronization.

Watch out — No obvious issues found. Sandbox test: successfully installed and registered in a new profile. Static checks found no problems.

The verdict — I would install it because it can provide one-click official price synchronization, but the premise is using official channels.

What it is — dsh-damage-pulse is a DeepSeek Harness plugin. It records DeepSeek token usage, per-call and session costs, and presents them in the DSH Web UI with cache-aware charge animations.

Who it is for — If you run long multi-turn conversations in DeepSeek Harness and need to track token consumption plus account balance at single-call, session and global levels, it fits. Users who do not care about token balance or want to skip the whale-girl feedback can skip it, because they may stick to the default Harness interface.

Watch out — It installs via npm. Static analysis shows it executes shell commands. Sandbox test passed: it installs cleanly in a fresh profile and registers into the profile. No obvious issues found.

The verdict — I would install it because it keeps a persistent ledger for token usage and animates charges via the whale-girl character, but only if I need cache-aware per-call cost tracking.

What it is — TokenLedger is a sidebar panel for attributing token usage to the relay sites serving requests, based on provider configurations.

Who it is for — If you need to track token usage distribution across multiple relay sites in DeepSeek Harness, this plugin would be suitable because it automatically discovers site attribution from existing configs. If your needs focus on token balance monitoring for a single provider without breakdowns, you might not need it.

Watch out — Sandbox testing passed in a fresh profile. Static checks indicate it will execute shell commands. No obvious issues found.

The verdict — If I were using it for token accounting across relays, I would install it because it reads from existing configurations without extra setup.

What it is — dsh-usage-stats provides multi-provider account monitoring and token usage analytics for the DeepSeek Harness web GUI.

Who it is for — When using DeepSeek Harness web profile for multi-provider token usage analysis and account balance monitoring, it is suitable to install. If a user only needs to analyze token usage for a single provider without cross-provider data aggregation, they can monitor using other methods.

Watch out — Requires providing API key or token to fetch account data. Sandbox testing passed: installed in a fresh profile and registered by Harness. Will execute shell commands.

The verdict — If multi-provider token usage and balance analysis is needed, I would install it because it offers fee estimation and budget alerts, but the premise is that credentials are provided.

What it is — DeepSeek Harness plugin adds a personal configuration section with token usage statistics, personalized custom instructions and a desktop pet.

Who it is for — If you need to view token usage and model distribution in DeepSeek Harness, then this plugin is suitable for you. If you do not use the workspace instruction feature in DeepSeek Harness, then you do not need to install it.

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

The verdict — I would install it because it provides model cost estimation and a usage-driven desktop pet, but only if token usage tracking is needed.

What it is — It provides a persistent dock, token usage panel, and activity heatmap.

Who it is for — When managing token usage in DeepSeek Harness web profile, if you need real-time balance monitoring and custom interface layout, this plugin fits. If you only need simple statistics without cross-channel comparison, you can skip installing it.

Watch out — Sandbox test passed: installed in fresh profile and registered by harness. The plugin runs locally only with credentials not exposed. No obvious issues found.

The verdict — I would install it because it integrates multiple widgets into a single persistent dock, but the premise is that the profile version matches.

What it is — This DeepSeek Harness plugin provides official balance, per-session cost and tokens, third-party token totals, recharge shortcut, and low-balance alerts.

Who it is for — When you need to view official DeepSeek balance and costs during a DeepSeek Harness session, this plugin is suitable. If you only want to view third-party token totals without the official recharge shortcut, you can skip installing it because this plugin focuses on official DeepSeek integration.

Watch out — Static checks indicate it will execute shell commands, but sandbox testing passed. It installs in a new profile and registers into Harness. No obvious issues found.

The verdict — I would install it because it allows local calculation of custom third-party pricing.

What it is — DeepSeek Harness Control Center for monitoring official balance, per-session costs and tokens, third-party token totals, completion alerts, official recharge, and flexible layouts.

Who it is for — When using the v4-flash model for sessions needing official balance and peak pricing monitoring, you can install this plugin because it supports v4 peak/off-peak ring clock and provider-aware composer surfaces. If you are not concerned with official pricing peak/off-peak rules, you can install this plugin because it supports Z.ai Coding Plan quotas adapter.

Watch out — Sandbox testing passed: installed in a fresh profile and registered with harness. No obvious pitfalls found.

The verdict — I would install it because it provides a 365-day local usage ledger with custom third-party pricing.

What it is — DeepSeek Harness plugin that aggregates session logs to display model calls, token usage, and cost estimates in the sidebar.

Who it is for — When using DeepSeek Harness for multi-provider LLM sessions and needing to track actual token consumption and costs, this plugin provides a sidebar entry. If sessionPersistence is unavailable, you do not need this plugin because it relies on persisted session logs for aggregation.

Watch out — It was tested successfully in a fresh profile and registered into the profile. No obvious issues found.

The verdict — I would install it because it aggregates real logs for multi-provider usage and cost estimation.

What it is — DSH Token Pet is a desktop pet plugin for DeepSeek Harness that visualizes real-time token occupancy and status animations from DSH events.

Who it is for — When using DeepSeek Harness for extended conversations and needing to track token consumption, this plugin provides intuitive status display. If you prefer pure text-based log viewing over desktop interface, this plugin offers a different data presentation approach.

Watch out — Sandbox test succeeded with successful installation and registration in a fresh profile. No obvious issues detected.

The verdict — I would install it because it provides a persistent cross-session Lifetime Ledger and background incremental indexing, ensuring historical data consistency.

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.

What it is — The dsh-save-money plugin automatically pauses and resumes tasks during user-defined time windows to avoid peak-hour API costs and displays account balance with a 10-minute spend bar chart.

Who it is for — This plugin suits you if you run long-running LLM tasks on DeepSeek Harness during peak pricing hours using the official API to save costs. Users who primarily use non-official API providers or focus on other resource savings can skip it.

Watch out — Sandbox testing passed with no obvious issues. The plugin manages pause and resume schedules and displays account balance and spend data.

The verdict — I'd install it because it automatically avoids peak API costs for DeepSeek Harness users during specified times, but only if I define the windows myself.

What it is — Generates deterministic agent reports from DeepSeek Harness session logs.

Who it is for — Suitable for analyzing agent runtime costs and tool call counts. If users need real-time monitoring of agent status without generating reports, this plugin is not applicable.

Watch out — Sandbox test passed, installed successfully in a fresh profile and registered with harness. No obvious issues found. Report generation is deterministic and local, not consuming model tokens.

The verdict — I would install it because it provides deterministic insights into agent performance based on 8 rules, provided that it is used within a DeepSeek Harness environment for post-session analysis.

What it is — Displays cache hit, miss, and output costs in the context menu popover.

Who it is for — If you are using DeepSeek models for long-context tasks and want to monitor cache costs to decide when to switch windows, this plugin is suitable. If you primarily use non-official DeepSeek routes, you do not need this plugin.

Watch out — Sandbox testing passed in a fresh profile. The plugin registers successfully into the profile. No obvious pitfalls discovered.

The verdict — I would install it because it provides specific data on cache costs to support data-driven window switching decisions.

What it is — This plugin displays OpenCode Go plan usage statistics, featuring consumption percentages for rolling, weekly, and monthly periods in a floating format with mini area charts, using background sampling against the official /v1/usage API.

Who it is for — If you need to monitor OpenCode Go plan usage in DeepSeek Harness, this plugin is suitable. If you want to install plugins with a single npm command, this plugin does not apply since it is a subdirectory plugin.

Watch out — Sandbox testing has not been performed. No issues were found in static checks.

The verdict — I would not install it because it can only be installed as a subdirectory plugin and is not published to npm.

What it is — This plugin provides a multi-provider usage stats framework for DeepSeek Harness, including built-in adapters for DeepSeek official and OpenCode Go, and supports hot-swappable single-file mjs adapters.

Who it is for — This plugin is suitable for scenarios requiring usage tracking across multiple providers in DeepSeek Harness. It is unnecessary for those who do not want to hot-swap adapters from the settings page.

Watch out — Sandbox test passed: installed successfully in a fresh profile and registered by harness. Static check notes execution of shell commands, but no obvious issues found.

The verdict — I would install it because its built-in adapters work even without an official usage endpoint.

What it is — Real-time display of token usage and generation speed in DeepSeek Harness Web UI.

Who it is for — When needing to track token consumption in real time in the DeepSeek Harness Web UI, it is suitable to install this plugin. Users not using remote connection do not need to install it.

Watch out — No obvious pitfalls found. Static checks revealed no issues.

The verdict — I would not install it because it is a sub-feature of dsh-web-ui.

What it is — Delivers a layered token-optimization pipeline for DeepSeek Harness, including output ladder, MCP lazy loading, compaction driver and cache-hit reporting. Built on real DSH plugin APIs for token savings in long sessions.

Who it is for — You should install it when working with DeepSeek models in long sessions involving heavy text input to reduce token usage. If your sessions do not involve MCP tools or repeated tool output reads, you do not need it—because MCP lazy loading and output ladder address exactly those scenarios.

Watch out — Installation requires cloning from GitHub and manually allowing the build script. The text2img module requires DEEPSEEK_API_KEY and PowerShell plus .NET System.Drawing on Windows. Sandbox testing passed, but web deployments need the core compaction-basic backend enabled.

The verdict — I would install it because it delivers real 40-60% token savings for long sessions with safe fail-open degradation, but only if your profile can handle the required web deployment patches in cordis.patch.yml.

What it is — This plugin provides a multi-platform API balance and usage dashboard for the DeepSeek Harness web GUI, showing balances, per-session and per-subagent costs, and an optional draggable whale widget.

Who it is for — Users who manage multiple platforms in the DeepSeek Harness web GUI are suitable for installing this plugin. If you do not use the DeepSeek Harness web GUI, you can skip installing it.

Watch out — Sandbox test passed: installed in a fresh profile and registered by harness, running normally. No obvious issues found.

The verdict — I would install it because it can automatically discover relays and determine official connections.