What it may solve
DSH Token 消耗体系Plugin:会话级实时费用徽标(逐Request模型×时代×峰谷计价)+ 全局用量看板(设置页)+ Coding Plan 订阅额度监控(GLM/Kimi,可扩展适配器)——实时、历史、余量三位一体
Imported third-party catalog description; not a Registry verification conclusion.DSH Token 消耗体系Plugin:会话级实时费用徽标(逐Request模型×时代×峰谷计价)+ 全局用量看板(设置页)+ Coding Plan 订阅额度监控(GLM/Kimi,可扩展适配器)——实时、历史、余量三位一体
Author: nanami-0713 · Usage & Billing · Catalog snapshot: 2026-09-19Canonical semantic path
DSH Token 消耗体系Plugin:会话级实时费用徽标(逐Request模型×时代×峰谷计价)+ 全局用量看板(设置页)+ Coding Plan 订阅额度监控(GLM/Kimi,可扩展适配器)——实时、历史、余量三位一体
Imported third-party catalog description; not a Registry verification conclusion.— stars · 251 downloads
Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19Active analysis coverage 5/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: 0 stars, 4 commits, 0 forks, and 0 watches; latest commit 2026-08-28.
Conclusion: Resolved npm release 1.0.1, published 2026-08-28, license MIT.
Installation and startup verification has not been run.
Dependency audit has not been run.
The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.
Conclusion: The static risk scan could not complete because package validation did not pass.
Conclusion: Package structure or integrity validation did not pass.
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 @hsinsekai-nanami/dsh-usage. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
@hsinsekai-nanami/dsh-usageAnalyzed 1.0.1github:nanami-0713/dsh-usageExact version not resolved