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

dsh-plugin-token-usage

Automated evidence available

GitHub-style token usage heat map for DeepSeek Harness — day/week/month granularity, per-model breakdown, hover-today badge. Read-only, fully local.

Author: Hjay1101 · Git & Code Review · Catalog snapshot: 2026-09-19

Canonical semantic path

Usage, Cost & Resource GovernanceConsumption Metering & ObservabilityToken Usage Analytics & Visualization

One primary path; alternate capabilities remain separate.
chat.model-tool-usage-reportinterface.heatmap-widgetinterface.theme-nativesessions.local-log-parsing

What it may solve

GitHub-style token usage heat map for DeepSeek Harness — day/week/month granularity, per-model breakdown, hover-today badge. Read-only, fully local.

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

Sources and public signals

Hjay1101/dsh-plugin-token-usage

1 stars · — 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 5/5. Historical chains are retained but do not count toward current coverage.

Analysis complete

Source structure

Conclusion: The source structure check completed without finding a structural issue.

Analysis complete

Repository health

Conclusion: The GitHub repository is reachable and not archived. Public data: 1 stars, 4 commits, 0 forks, and 0 watches; latest commit 2026-09-06.

Analysis complete

npm release

Conclusion: This plugin has no npm package source, so this item does not apply.

Analysis complete

DSH compatibility

Conclusion: Compatibility verification did not pass: the bounded compatibility check did not pass. Test environment: DSH 0.1.6-alpha.2, web profile.

Analysis complete

Dependency audit

Conclusion: The dependency audit did not produce a complete report.

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 bounded static scan found none of its predefined risk signals. This is not proof of safety.

Analysis complete

Package integrity

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.

Continue with the latest plugin manager

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