01
QUICK ANSWER
What is the dsh-usage-stats plugin?
Multi-provider usage dashboard with provider/model token breakdowns, calendar drill-downs, account balances, and OpenCode Go / Z.ai subscription quota tracking.
Learn what dsh-usage-stats does, decide whether it fits a DeepSeek Harness workflow, and find the verified upstream installation path.
- Plugin type
- Usage & Billing
- Install target
- DeepSeek Harness
- Upstream
- @Ychris12138
02
CORE FEATURES
dsh-usage-stats plugin features
The capabilities below are derived from the upstream description captured for dsh-usage-stats. Use them to compare the plugin with other usage & billing options before installation.
Multi-provider usage dashboard with provider/model token breakdowns, calendar drill-downs, account balances, and OpenCode Go / Z
ai subscription quota tracking
03
USE CASES
dsh-usage-stats use cases
dsh-usage-stats is most relevant when a DeepSeek Harness workflow needs one or more of these usage & billing outcomes.
Monitor session cost
Compare provider usage
Set practical budget awareness
04
INSTALLATION
How to install dsh-usage-stats
Review the repository and the command in its current README before execution. The command below was captured from the public directory or the maintainer documentation.
dsh plugin --profile web add github:Ychris12138/dsh-usage-stats- InspectRead the repository, dependencies and requested configuration.
- InstallRun the command for the intended DSH profile.
- Restart & verifyRestart Harness and test in a disposable workspace.
Run the upstream installation command for the intended profile, restart that DeepSeek Harness process, and confirm the plugin appears before granting it access to a real project.
If you are new to plugin profiles, read the DeepSeek Harness installation guide before changing an active environment.
05
SOURCE & SAFETY
dsh-usage-stats GitHub repository and safety
GitHub repositoryhttps://github.com/Ychris12138/dsh-usage-statsThis is third-party code that can run with your local permissions. Review the repository, dependencies, install scripts, network access and requested credentials; pin a commit when reproducibility matters.
Registry sourced means the name, description and install path were taken from public project records. It does not mean this site completed a runtime test or security audit.
The record was last checked on 2026-08-19. Reconfirm the current README, release notes and requested permissions because upstream behavior can change after this snapshot.