DeepSeek Harness becomes the eighth plugin door, and it needed no second package. antislop already shipped as antislop-ai; that same package now declares a DSH bundle, so installing it by name from the Plugins page loads all six skills without copying a file.
One package, two jobs
antislop-ai still installs skill folders into any of thirteen agents. It now also carries a dsh.bundle.patch and an exports entry for ./dsh, which is what DeepSeek Harness reads when it treats the package as a plugin bundle.
The patch inserts one row, antislop-ai/dsh. That entry registers a skill provider, and the provider reads the six SKILL.md files straight out of the installed package.
The skills arrive at the bundled rank, so a folder install of the same skill still outranks it. A machine with both ends up with one copy in charge, the one the user put there.
The installer covers it too
DeepSeek Harness joins the installer's agent list and reads the shared .agents/skills folder, the same one Antigravity, Copilot, Kimi Code, and Amp use. It is the fifth agent on that folder, so picking it beside any of them installs once.
The installer now covers thirteen agents over nine folders, and the guide lists the new door with its install, update, and remove steps.
What is verified, and what is not
The repository check gained a case for the bundle: the patch path must exist, dsh/ must be in files, and every patch row must name a subpath the package actually exports. The smoke test imports the plugin, registers a provider the way DeepSeek Harness does, and compares the six names against the skill folders.
The package was packed and installed into a fresh DSH profile on this machine. The profile composed with the antislop-ai/dsh row and raised no activation warning, and importing the installed plugin listed all six skills, each with its body and its own skill folder as the resource base.
Two things are not verified here: an install straight from the npm registry, and the skill list inside the desktop app. Both need a published package and a signed-in account, so they land with this release rather than before it.
Updating
DeepSeek Harness lists an update when a newer antislop-ai reaches npm. If the button does not appear, remove the plugin and add it again, which fetches the newest release.
The installer route is unchanged:
npx antislop-ai --updateA plugin keeps its own copy, so update it through DeepSeek Harness. Skills load when a session starts, so start a new one afterwards. Full detail is in the ROADMAP.