DSH Plugin Registry
中文EN
Submit plugin
Plugins/dsh-token-usage

dsh-token-usage

Automated evidence available

Detailed model usage and cost analysis, with per-session usage stats and usage queries for GLM, MiniMax, OpenCode Go, DeepSeek and more.

Author: LaoYueHanNi · Usage & Billing · Catalog snapshot: 2026-09-19

Canonical semantic path

Usage, Cost & Resource GovernanceConsumption Metering & ObservabilityPre-call Cost Estimation

One primary path; alternate capabilities remain separate.
interface.web-ui-dashboardmodels.pricing-tablesprovider.quota-querysessions.per-session-stats

What it may solve

Detailed model usage and cost analysis, with per-session usage stats and usage queries for GLM, MiniMax, OpenCode Go, DeepSeek and more.

Imported third-party catalog description; not a Registry verification conclusion.

Sources and public signals

LaoYueHanNi/dsh-token-usage

12 stars · 2062 downloads

Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19

What can currently be confirmed

Active analysis coverage 1/5. Historical chains are retained but do not count toward current coverage.

Not analyzed

Source structure

Source structure has not been analyzed.

Not analyzed

Repository health

Repository metadata has not been analyzed.

Not analyzed

npm release

npm release metadata has not been analyzed.

Analysis complete

DSH compatibility

Conclusion: Compatibility verification passed. Installation, profile loading, and sustained startup all completed. Test environment: DSH 0.1.6-alpha.2, web profile.

Analysis complete

Dependency audit

Conclusion: This bounded audit reported 0 known vulnerabilities. It covers only the locked versions and audit source; zero reports is not proof of safety.

Not analyzed

Functional verification

The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.

Analysis complete

Static risk scan

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.

Analysis complete

Package integrity

Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: @laoyuehanni/dsh-token-usage@0.4.3; SHA-256: 1a0e1fc87f43a16a9bc37cd37dcdfd697995f048b71894faf73501b10477be4f.

Automated evidence is scoped to the named artifact, DSH target and profile. It is not a blanket safety or feature-completeness claim.

Continue with the latest plugin manager

Describe your task in a DSH conversation and mention dsh-token-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.

Install or update the plugin manager (latest)