DeepSeek Harness Plugin Collection: Cost Metrics and Browser Use

The core architecture of DeepSeek Harness (DSH) is “everything is a plugin.” During actual development and debugging, developers usually need to monitor API call costs and perform browser automation. The dsh-plugins repository provides ready-to-use implementations for both of these scenarios and is maintained by icedrop-lab.

This is a pnpm monorepo that includes two independent plugin packages and one aggregate package. It addresses the need in the DSH environment to fetch cost data, check balances, and perform browser automation tasks.

Core Features¶

Cost Metrics and Balance Display
Provides a balance/Token widget in the session header, supports a sidebar fallback display, and offers a DeepSeek top-up link.

Browser Use Tool
Provides a browser_use tool for models, powered by the browser-use CLI.

Aggregate Package
Provides the dsh-all package, which can install the above two plugins at once.

Installation¶

Install with npm (Recommended)¶

Install a single plugin or the aggregate package directly using the official command. A service restart is required after installation.

dsh plugin --profile web add @icedrop-ai/dsh-cost-meter
dsh plugin --profile web add @icedrop-ai/dsh-browser-use
# Or install the aggregate package directly
dsh plugin --profile web add @icedrop-ai/dsh-all

Install with a Git Subpath (No Build Approval Required)¶

When installing from a Git subpath, the plugin directly uses the committed lib/ directory in the repository, so build approval is not required. A fixed tag or commit SHA must be specified during installation; pointing to the main branch is not allowed.

dsh plugin --profile web add \
  "git+https://github.com/icedrop-lab/dsh-plugins.git#v0.1.0&path:packages/cost-meter"

Usage Steps¶

Run the installation command above.
Restart the dsh web service.
Use the dsh --profile web --dump-config command to confirm that the # == ... layer exists in the configuration.

Notes¶

Version pinning: For both npm installation and Git subpath installation, it is recommended to pin a tag or commit SHA and avoid pointing to the main branch.
Early version compatibility: Before the aggregate package is published on npm, it is recommended to use a separate tarball or a Git subpath installation method.