AI Agent Hub
Back to plugins
🧰

dsh-trapstreet

Web Tools Updated 2026.08.23

Run the following command in DeepSeek Harness:

dsh plugin install trapstreet/dsh-trapstreet

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install trapstreet/dsh-trapstreet in DeepSeek Harness to install this plugin; the source is available at https://github.com/trapstreet/dsh-trapstreet .

About this plugin

You installed a dozen DeepSeek Harness plugins, yet you cannot say which ones are actually contributing a tool and which are silently parked in the loader tree registering nothing. dsh-trapstreet shines a light on the grey zone between installed and useful: it reads the live loader tree inside the running harness in-process, with no network call, no API key, and no subprocess, and in a single invocation pins down which of the seven failure states each plugin is in.

Two tools cover two ends. trapstreet_checkup handles local diagnosis, surfacing install failures, plugins that never entered the loader tree, and modules that fail to load at a glance; add classify and it also labels each plugin against the community directory. trapstreet_boards handles the community side, pulling read-only evaluation boards from trapstreet.run to show what a board tests, which commit is pinned, and which entries come from a DeepSeek model, with new boards appearing automatically.

Built for Harness users running multiple plugins: after chasing down why the agent reports no new capability, use it to confirm the loader is not the culprit; or if you want a quick look at community evaluation baselines without spinning up your own run, grab a board id and read the details.

Use Cases

  • Find out which installed plugins actually register tools and which sit silently in the loader tree
  • Diagnose loader state in headless or sandboxed environments where dsh --dump-config hits permission errors
  • Inspect public evaluation boards for test scope, pinned commit, and DeepSeek model entries without running your own tests

Best For

  • Developers running multiple DeepSeek Harness plugins who need to verify load state
  • Engineers debugging plugin tree-entry issues in headless or restricted environments
  • Users who want a quick look at community evaluation baselines without spinning up their own runs