AI Agent Hub
Back to plugins
🧩

dsh-plugin-guardian

admin-security Updated 2026.08.18

Run the following command in DeepSeek Harness:

dsh plugin install Nico0713520/dsh-plugin-guardian

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

Run dsh plugin install Nico0713520/dsh-plugin-guardian inside DeepSeek Harness to install this plugin; the full source repository is available at https://github.com/Nico0713520/dsh-plugin-guardian .

About this plugin

DeepSeek Harness went from zero to nearly six thousand plugins in a single week, yet nothing watches the interactions between them. A skin you install can silently break another plugin, two plugins registering the same tool name crash the harness at startup, and a plugin your agent sketches in Creator mode vanishes the moment you restart. dsh-plugin-guardian makes all of that visible and fixable before it bites you.

Four tools cover the full plugin lifecycle. plugin_doctor performs a read-only health check on a single plugin directory, plugin_profile_scan sweeps the entire installed set for cross-plugin tool-name collisions and version skew, plugin_promote atomically writes an ephemeral Creator-mode plugin to a provenance-marked staging directory so it survives a restart, and plugin_install runs an audit-first guided flow that only executes when you explicitly approve. Every finding carries a confirmed, inferred, or unknown confidence tag, so a static pattern is never presented as proof of a runtime bug.

Built for developers and teams who install, maintain, or generate DeepSeek Harness plugins regularly, especially those juggling multiple plugins who need to verify tool-name uniqueness, confirm that a community package is structurally sound before shipping, or promote an agent-authored plugin to-lasting storage. plugin_doctor and plugin_profile_scan are strictly read-only: they never execute source, spawn subprocesses, hit the network, or write a single file.

Use Cases

  • Scan the installed plugin set before adding a new one to catch tool-name collisions and version skew
  • Run a read-only health check on a community plugin with three-tier confidence reporting
  • Promote an ephemeral Creator-mode plugin to a durable, provenance-marked asset in one step

Best For

  • Developers juggling multiple DSH plugins who must verify tool-name uniqueness
  • Contributors and maintainers in the DSH plugin ecosystem preparing cross-plugin conflict scans before release
  • Teams using agent-generated plugins that need promotion to durable storage to survive restarts