Max-Samson/dsh-usage-chart
C3A DeepSeek Harness Web plugin for real-time Token usage, cost estimates, per-round charts, and DeepSeek API balance.
★ 5+ · Max-Samson/dsh-usage-chart source on GitHub · this plugin in the registry
Max-Samson/dsh-usage-chart is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, executes system commands, uses eval / new Function, reads credential-class env vars.
Installable plugin — declares a dsh.bundle manifest
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ./cordis.patch.yml |
| executes system commands | exec | ×3 in authored code, e.g. build.mjs:14, build.mjs:14 |
| uses eval / new Function | eval | ×8 in authored code, e.g. scripts/verify-render.mjs:41, scripts/verify-render.mjs:61 |
| reads credential-class env vars | token_env | DEEPSEEK_API_KEY |
Services it injects
locale sessions slots webServer
Outbound domains
api.deepseek.com open.er-api.com api.frankfurter.dev
Environment variables it reads
DSH_PLUGIN_ID DSH_PROBE_CHROME PROGRAMFILES LOCALAPPDATA DSH_PROBE_URL DSH_PROBE_ARTIFACTS DSH_PROBE_SESSION DEEPSEEK_API_KEY
How to read this
Levels measure capability surface and transparency, not maliciousness. A C3 plugin can be entirely legitimate — a desktop shell genuinely needs subprocesses. The point is that you can see this before installing. See the levels explained and how dsh plugins work.
Findings come from static analysis of shipped code; nothing is executed. Think a flag is wrong? Open an issue — every flag cites the file and line it came from.