DeepSeek Harness's 35k Plugin Count Is a Mirage: Only ~1k Actually Install
The gap between claimed and working plugins signals a governance vacuum that costs users real time and security: permissions are effectively unchecked, plugins conflict, and upgrades wipe configs. For anyone building atop an agent shell, the lesson is to audit the ecosystem you adopt and treat plugin counts as marketing, not engineering metrics.
DeepSeek Harness's plugin ecosystem claims 35,000 third-party plugins, but that number does not survive contact with reality. A manual inspection of 11,000 repositories found only about a thousand that can actually be installed per the project's own rules. The official announcement on November 5 said roughly 35k, dshmarket lists 10,778, GitHub's `dsh-plugin` tag shows 31,259, and a Leiphone screening found 1,883 public rejections, 93% due to "cannot install per dsh rules." The root cause is that there is no authoritative definition of a plugin: the only guidance is to add the tag to your repo, with no approval or actual connection to dsh. The result is a pile of mislabeled repositories, including a 2020 resume generator ranking fourth in best-match search and 505 repos named `deepseek-harness-desktop`.
The ecosystem's lack of governance extends to permissions and stability. A probe plugin succeeded in all nine tests even under the read-only tier, reading `~/.ssh` files and API keys from environment variables, writing to `/tmp`, and connecting to the internet. Plugins bypass permission checks because they are the shell itself, making the tier system effectively decorative. Real-world failures are common: the top ten plugins by downloads conflict when installed together, a version upgrade wiped 32 plugin entries and shrank configuration from 34 to 2 items requiring five hours of manual repair, and installing plugins invalidates the KV cache with no user-facing warning. The only practical advice is to check source, dependencies, permissions, and backups before installing anything.
The lack of a plugin definition means the ecosystem's size is mostly decorative; the genuinely functional subset is tiny and dominated by utilities that provide visibility or safety, not novel capabilities.
The permission model is fundamentally broken: plugins bypass the tier checks because they are the agent shell itself, making read-only mode meaningless and turning installation into unconditional consent.
Category data shows most plugin usage is cosmetic (UI enhancements outnumber capability extensions), suggesting users prioritize interface customization over agent intelligence.
The cost structure revealed by dsh-cost-meter indicates optimization should target tool call frequency and return payload size, not model pricing, which is counterintuitive but concrete.