The dsh-plugin topic is polluted by non-DSH repos — worth adding a guideline?

[ylwl1997]

Hi DeepSeek Harness team 👋

We run dshbase, a community plugin directory for DeepSeek Harness. While auditing our own catalog, we discovered that the dsh-plugin GitHub topic is significantly polluted: many repos tag themselves dsh-plugin for visibility but are not actually DSH plugins.

A few concrete examples (all currently in the topic, all high-star):

• openhanako (~6k★) — a personal AI agent with memory/personality, no bundle manifest, no relationship to DSH.
• EchoBird (~3k★) — a "model switch across 20+ coding agents" tool.
• exo (~650★) — a different harness entirely.
• synergy (~540★) — a general-purpose agent.

A real DSH plugin ships a bundle manifest (cordis.patch.yml / cordis.yml) and installs via dsh plugin add. These don't.

Why this matters: the topic is the de-facto registry. Directories that trust it unverified (e.g. the awesome-dsh-plugin list and the dsh-suite catalog) end up listing these as "plugins", which misleads users and erodes trust in the whole ecosystem. We removed 19 such projects from our own directory after this audit.

Our suggestion: it would help enormously if the official project published a short guideline for what qualifies as a dsh-plugin (bundle manifest + installable via dsh plugin add), and ideally a curated/verified list. We'd be glad to contribute our verification tooling (bundle-manifest check + LLM README review) if useful.

Happy to share the full list of tag-squatters we found if that helps.

— the dshbase team (dshbase.com)

---

中文简述：我们发现 dsh-plugin topic 被大量非 DSH 仓库蹭标签（如 openhanako 6047★ 是独立 AI agent、EchoBird 3016★ 是跨工具切换器、exo 是另一个 harness）。真正 DSH 插件应带 bundle 清单（cordis.patch.yml）且能 dsh plugin add 安装。建议官方出个「什么算 dsh-plugin」的规范，最好维护一份官方精选列表，避免生态被污染。