dsh-chat-cost

Automated evidence available

Live token cost for every chat in the DSH Web UI: the chat, its subagents and the whole session tree, priced from a bundled models.dev snapshot of seven providers and 139 priced models, with cache read and write rates wherever the provider publishes them and DeepSeek from its own peak and off-peak table. Every finished answer carries its own price in the transcript, and a chat that is not currently open is priced from the log instead of disappearing. Spend is costed per interval from an append-only JSONL ledger in the project folder, so logged work keeps the tariff it was billed at. On top of it: budget-aware work plans packed against a money limit, routing scenarios that show which models are worth connecting, a generated plan document in English, Chinese or Russian, and a warning when spend belongs to no plan unit.

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

Canonical semantic path

Usage, Cost & Resource GovernanceConsumption Metering & ObservabilityCost Estimation & Real-time Cost Display

One primary path; alternate capabilities remain separate.

What it may solve

Live token cost for every chat in the DSH Web UI: the chat, its subagents and the whole session tree, priced from a bundled models.dev snapshot of seven providers and 139 priced models, with cache read and write rates wherever the provider publishes them and DeepSeek from its own peak and off-peak table. Every finished answer carries its own price in the transcript, and a chat that is not currently open is priced from the log instead of disappearing. Spend is costed per interval from an append-only JSONL ledger in the project folder, so logged work keeps the tariff it was billed at. On top of it: budget-aware work plans packed against a money limit, routing scenarios that show which models are worth connecting, a generated plan document in English, Chinese or Russian, and a warning when spend belongs to no plan unit.

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

Sources and public signals

igormel81/dsh-chat-cost

0 stars · 2023 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: may create or modify files, may access the network, may start external processes, test, example, or support code contains additional capabilities outside the default runtime scope. 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: dsh-chat-cost@0.6.11; SHA-256: 538840fd59d67f76aa9d944858ae3849875505efee7f6d6353dde5225f416b3f.

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-chat-cost. 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)