@takboo/dsh-usage-state

DSH plugin: show account balance (API mode) or coding-plan quota usage (5h/7d) for the model in use

PluginDeveloperNetwork

Verification

L4 · Install tested

Failed

Risk

LowRisk

Health

Active

Trust

Silver

Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.1-rc.2 · last checked 10-20Install verification details →

What it doesAI

DSH plugin that shows your account balance (API mode) or coding-plan quota usage (5h/7d) for the model currently in use.

Shows API-mode account balance for the model in use
Displays coding-plan quota usage for 5h and 7d windows
Ties the shown usage state to the active model

developerAI

Capability tags are AI-inferred or rule-extracted from the README (see badge) — vocabulary-limited, not install-verified. AI = inferred; README = literal keyword from the readme.

Installation

dsh plugin --profile web add dsh-usage-state@0.4.8

security scan passed · npm package v0.4.8

Install method: npm · sandbox install ok, web smoke failed (L5)

Verification & Compatibility

Grouped by plugin version: each card lists the dsh versions actually tested against that artifact version and their install verdicts (L5 wins). Untested combinations are omitted — absence means untested, never assumed compatible. L1–L3 are a plugin-level static archive (independent of the dsh version — the same verdict on every dsh row): they sit in each row's level grid next to L4/L5, marked "static", while their evidence is stored once per plugin inside that row's "checks & evidence" instead of being duplicated per version.

External credentials (plugin-level): none detected

Declared DSH compatibilityfrom package.json · peerDependencies

author declared no dsh version requirement

○ The author declares no dsh version requirement — install is not blocked by version.

Install compatibility matrix (rows = plugin versions〔latest 5〕, columns = dsh versions〔latest 5〕)

At-a-glance → evidence in the cards below

plugin ＼ dsh	dsh 0.2.1-rc.2 current	dsh 0.2.1-alpha.2
0.4.8	✗	·
0.4.6	·	·
0.4.5	·	✗
v0.4.5	·	·

Install compatibility (by plugin version, dsh versions within)

Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed

0.4.8npm1 failed2026-10-20

dsh-usage-state

✗dsh 0.2.1-rc.2current2026-10-20L5 · failed

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-rc.2
• Plugin artifact: npm · dsh-usage-state@0.4.8

Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)

L1 static

Passed

L2 static

Passed

L3 static

Passed

L4 sandbox

Passed

L5 runtime

Failed

Sandbox install failed

L5 · failed

ID: dsh-usage-state@0.4.8@dsh0.2.1-rc.2 · profile: l4-sandbox

Issued: 2026-10-20 · expires: 2026-10-27

View checks & evidence

L1 · Found✓ Passed

Defaulted from L3L1.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L2 · Structured✓ Passed

Defaulted from L3L2.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L3 · Install spec✓ Passed

Install command parsedL3.1_INSTALL_COMMAND_PARSED✓ Passed

Source: registry verification · Method: install spec parse · Captured 2026-10-18

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

Source: registry verification · Method: DSH version declaration · Captured 2026-10-18

L4 · Install tested✓ Passed

Install executed in confined sandboxL4.1_INSTALL_EXECUTED_CONFINED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-20

spec dsh-usage-state · channel npm package · outcome ran · exit 0

check took: 6.8s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-20

spec dsh-usage-state · channel npm package · outcome ran · exit 0

check took: 6.8s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-20

spec dsh-usage-state · channel npm package · outcome ran · exit 0

check took: 6.8s

L5 · Run tested✕ Failed

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-20

spec dsh-usage-state · install mode reused L4 scratch

check took: 0ms

Web boot readyL5.2_WEB_BOOT_READY✕ Failed

plugin tree failed to load

HTTP endpoint servedL5.3_HTTP_SERVED✕ Failed

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

0.4.6npm2026-10-15

dsh-usage-state

No runtime install test for this version (static scan only) — compatibility unknown, never assumed.

0.4.5npm1 failed2026-10-14

dsh-usage-state

✗dsh 0.2.1-alpha.22026-10-14L5 · failed

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-alpha.2
• Plugin artifact: npm · dsh-usage-state@0.4.5

Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)

L1 static

Passed

L2 static

Passed

L3 static

Passed

L4 sandbox

Passed

L5 runtime

Failed

Sandbox install failed

L5 · failed

ID: dsh-usage-state@0.4.5@dsh0.2.1-alpha.2 · profile: l4-sandbox

Issued: 2026-10-14 · expires: 2026-10-21

View checks & evidence

L1 · Found✓ Passed

Defaulted from L3L1.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L2 · Structured✓ Passed

Defaulted from L3L2.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L3 · Install spec✓ Passed

Install command parsedL3.1_INSTALL_COMMAND_PARSED✓ Passed

Source: registry verification · Method: install spec parse · Captured 2026-10-18

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

Source: registry verification · Method: DSH version declaration · Captured 2026-10-18

L4 · Install tested✓ Passed

Install executed in confined sandboxL4.1_INSTALL_EXECUTED_CONFINED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14

spec dsh-usage-state · channel npm package · outcome ran · exit 0

check took: 12.7s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14

spec dsh-usage-state · channel npm package · outcome ran · exit 0

check took: 12.7s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14

spec dsh-usage-state · channel npm package · outcome ran · exit 0

check took: 12.7s

L5 · Run tested✕ Failed

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14

spec dsh-usage-state · install mode reused L4 scratch

check took: 0ms

Web boot readyL5.2_WEB_BOOT_READY✕ Failed

boot failed

HTTP endpoint servedL5.3_HTTP_SERVED✕ Failed

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

v0.4.5github2026-10-14

https://github.com/takboo/dsh-usage-state

No runtime install test for this version (static scan only) — compatibility unknown, never assumed.

Author badges

Embed the official badges in your README to showcase security & install-test status:

Security Report

Two automated layers, neither a manual review: a static scan (per-plugin rule checks) and a model-driven dynamic security audit that covers only the subset static-flagged at warn or above and never executes plugin code.

dsh-usage-stateAutomated review · daily

Static low, dynamic no conclusion — stricter wins → overall low.

static low→dynamic no conclusion→overall low

0 critical·0 high

lowoverall · low

1static scan · vet primaryvet AST static analysis (npm artifact or git source)

Version binding

plugin versionv0.4.8dsh manifest

scanned version0.4.8npm2026-10-21

current version0.4.8same version

vet verdictclean · npm

Vet is an AST static scan (npm artifact or git source).

2dynamic auditmodel reads redacted source context · never executes plugin code

not in the dynamic queue (queue only covers plugins static-flagged at warn or above) — this does not mean the dynamic audit found it safe.

Rule: the dynamic audit can only raise risk, never lower it (raise-only, never an exemption); a wrong raise is withdrawn by human review and the tier falls back to the static verdict. Overall verdict = the stricter of the two layers.

Disclaimer: the static scan and the dynamic security audit are both automated analysis, not a security guarantee. Always review what you install.

Activity

Last commit 2026-10-19 · activity: Active

• Repo created: 2026-09-20

• Stars: ★ 0 · Forks: 1

• Health: Active — committed within last 30 days

Source

GitHub: github.com/takboo/dsh-usage-state

Plugin notes

What is the @takboo/dsh-usage-state DeepSeek Harness plugin?

@takboo/dsh-usage-state is a DeepSeek Harness plugin maintained by @takboo. It is cataloged on dsh.so as a Developer plugin, with a public GitHub source, declared install command, and automated static scan results; plugins static-flagged at warn or above also carry a model-driven dynamic security audit record.

How do I install @takboo/dsh-usage-state?

Run dsh plugin --profile web add dsh-usage-state@0.4.8 in a DeepSeek Harness (dsh) environment. This exact command has been verified by a real install inside an isolated windows-acl sandbox (L4).

How does the security scan relate to a manual audit?

Both layers are automated, not a manual audit: the static scan is heuristic analysis of the repository source (it can produce false positives and miss context), and the dynamic security audit has a model read the harvested source context with secret files stripped and content redacted inline — plugin code is never executed. The dynamic audit only covers plugins static-flagged at warn or above, and its conclusion can only raise the combined verdict, never exempt it. Neither layer is a manual security audit or an endorsement; before using a plugin, review the repository and installed permissions, and combine both with the verification level (L4/L5) and health signals.

"DeepSeek Harness (dsh) is an open-source agent harness developed by DeepSeek AI. It uses an architecture where everything is a plugin, and is powered by Cordis."
— DeepSeek Harness README

Sources: GitHub repository · DeepSeek Harness README · security scan data · Maintained by dsh.so · Last updated 2026-10-19

@takboo/dsh-usage-state

What it doesAI

Installation

Verification & Compatibility

Author badges

Security Report

Activity

Source

Author README