What it may solve
Per-model token usage and cost estimation with DeepSeek account balance, shown in a Settings panel tab.
Imported third-party catalog description; not a Registry verification conclusion.Per-model token usage and cost estimation with DeepSeek account balance, shown in a Settings panel tab.
Author: AKS1st · Usage & Billing · Catalog snapshot: 2026-09-19Canonical semantic path
Per-model token usage and cost estimation with DeepSeek account balance, shown in a Settings panel tab.
Imported third-party catalog description; not a Registry verification conclusion.7 stars · 638 downloads
Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19Active analysis coverage 4/5. Historical chains are retained but do not count toward current coverage.
Conclusion: The source structure check completed without finding a structural issue.
Conclusion: The GitHub repository is reachable and not archived. Public data: 7 stars, 30 commits, 0 forks, and 0 watches; latest commit 2026-09-14.
Conclusion: Resolved npm release 0.17.0, published 2026-09-14, license MIT.
Conclusion: Compatibility verification passed. Installation, profile loading, and sustained startup all completed. Test environment: DSH 0.1.6-alpha.2, web profile.
Conclusion: This bounded audit reported 0 known vulnerabilities. It covers only the locked versions and audit source; zero reports is not proof of safety.
The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.
Conclusion: The scan observed 4 code capabilities: contains credential or token handling code, may read environment variables, may create or modify files, may access the network. No predefined elevated-risk condition was triggered; this is not proof of safety.
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: model-usage-plugin@0.17.0; SHA-256: 58a1c7769835bf22fe0f90ea3f9ea9a92a8db1abe088f03df27519a414c1b5e5.
Automated evidence is scoped to the named artifact, DSH target and profile. It is not a blanket safety or feature-completeness claim.
Describe your task in a DSH conversation and mention model-usage-plugin. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
model-usage-pluginAnalyzed 0.17.0github:AKS1st/model-usage-pluginExact version not resolved