dsh-agent-plugins-market
The standard way to install Claude Code / Codex / Cursor / Kimi plugin marketplace suites in DeepSeek Harness (DSH) — zero conversion, zero file copying. Skills, MCP servers, hooks and slash commands are injected into your dsh sessions at runtime.
The plugin will be installed here. Keep web if you are unsure.
npx -y @deepseek-ai/dsh plugin --profile web add dsh-agent-plugins-market@0.7.1
Agent Plugins Market is published as dsh-agent-plugins-market and currently resolves to version 0.7.1. The Hub verifies its manifest and preserves the exact installation source for reproducible installs.
A plugin marketplace and agent capability workspace for DeepSeek Harness (DSH).
Reuse supported content from Claude Code, Codex, Cursor, Kimi and other recognized layouts, and manage your own skills, commands, agent personas, MCP services and LSP servers in the DSH Web GUI.
If this plugin is useful to you, a ⭐ on GitHub is appreciated.
English | 简体中文 | Documentation | npm
Quick start · Everyday use · Compatibility · FAQ
|
Market Market Add sources, preview suites, install and enable. |
Skills Skills Browse skills and author your own. |
Commands Commands Manage prompt templates invoked as /name. |
|
Agent personas Agent personas Roles with an exact provider, model and effort. |
MCP services MCP services Credentials, authorization and connection status. |
LSP servers LSP servers Language server configuration and runtime status. |
.plugin/, agent-plugins and manifest-less skill collections..zip / .tar.gz / .tgz / .tar); adopt a checkout you cloned yourself; refresh on demand; delete a managed checkout when you remove its source.auto follows the interface language, or choose global / China mainland — and the plugin routes github.com clones through the matching mirror. A proxy and per-invocation tuning live in the host config./name, agent personas into the subagent catalog, MCP tools with an mcp__ prefix, hooks onto host lifecycle events, and language servers through the lsp tool.${VAR} references resolve from the host credential store or the launch environment; per-server overrides disable or patch a declaration without editing the source; an optional host-client compatibility mode is available. Tools register as mcp__<suite>__<server>__<tool>.lsp tool mounts only while a language server is wanted. The server executable itself must be on PATH. Upgrading from a release that asked you to expose LSP from your profile? A profile that still carries that hand-added layer reports a seam conflict; the LSP panel names the file and removes the layer for you, keeping a backup.subagent_run, which starts a durable background child and returns its id immediately.~/.agents/, then edit them or disable them without deleting the files.Install into your profile, replacing <name> with its name:
dsh plugin --profile <name> add dsh-agent-plugins-market
https://github.com/anthropics/claude-plugins-official. No sources are preconfigured./ in chat to find its user-invocable skills. For an MCP suite, check MCP services and resolve any credential or connection notice before using its tools.Requirements, profile configuration and alternative installs: usage guide.
The workspace has six tabs:
| Tab | Use it to |
|---|---|
| Market | Add sources, preview suites, install / uninstall, enable / disable and refresh. |
| Skills | Browse skills and create or edit your own reusable instructions. |
| Commands | Manage prompt templates invoked as /name. |
| Agent personas | Manage role instructions and save an exact provider, model and reasoning effort per role; delegate in the background through subagent_run. |
| MCP services | Add a service or configure an installed one, its credentials and authorization; inspect status and retry failures. |
| LSP servers | Add and configure language servers and inspect their runtime status. |
A source is where content comes from; a suite is an installable unit discovered there. Adding a source discovers its suites. Installing and enabling a suite controls its runtime capabilities.
Everything you author yourself lives in the shared Agent layout root: skills, commands and personas as Markdown under ~/.agents/, and the MCP and LSP services you add in the workspace in ~/.agents/mcp.json and ~/.agents/lsp.json. Project-native resources stay in the project. See storage and discovery for paths and precedence.
All six tabs share a saved grid/list preference. Add and refresh actions sit at the top right; resource state rails are green when active.
Supported layout dialects describe how files are organized. The shared priority table lists suite manifests and Marketplace catalogs together. All ten layout contracts in schemas/ have independent reader tests; the layout audit maps them to pinned repository fixtures.
Supported runtime surfaces describe what DSH can use:
| Surface | Runtime support and conditions |
|---|---|
| Skills | Host skill catalog and user-invocable slash entries; supported root placeholders are expanded. |
| Commands | Slash commands through the host command service. |
| Agents | Dynamic subagent catalog and subagent_run; requires host agents, tools, LLM, subagent and session-persistence services. |
| MCP | Built-in bridge by default: stdio, Streamable HTTP with OAuth, and legacy SSE. Optional host-client compatibility mode is also available. |
| Hooks | The command-hook subset mapped by dsh-hooks-claude-code. |
| LSP | Self-provisioned: installing the plugin is the whole setup, and lsp mounts only while a language server is wanted; the server executable must be on PATH. |
Agent roles appear in the session catalog and run through subagent_run(agent, prompt). A role may save an exact provider plus model pair and a reasoning_effort; every other declaration is ignored and the child inherits the parent route. tools and disallowedTools are preserved in the file but never applied. See agent roles for the frontmatter fields and limits.
When multiple manifests exist in the same suite directory, the first existing file in this order selects the layout:
| Priority | Layout | Suite manifest | Marketplace catalog |
|---|---|---|---|
| 1 | agent-plugins / root compatibility | plugin.json | No dedicated catalog |
| 2 | Universal compatibility | .plugin/plugin.json | .plugin/marketplace.json |
| 3 | Claude Code | .claude-plugin/plugin.json | .claude-plugin/marketplace.json |
| 4 | Cursor | .cursor-plugin/plugin.json | .cursor-plugin/marketplace.json |
| 5 | Kimi Code | kimi.plugin.json, then .kimi-plugin/plugin.json | .kimi-plugin/marketplace.json |
| 6 | Codex | .codex-plugin/plugin.json | .agents/plugins/marketplace.json, then .agents/plugins/api_marketplace.json |
| 7 | ZCode | .zcode-plugin/plugin.json | No dedicated catalog |
| 8 | Qoder CLI | .qoder-plugin/plugin.json | .qoder-plugin/marketplace.json |
| 9 | GitHub Copilot CLI | .github/plugin/plugin.json | .github/plugin/marketplace.json |
| Fallback | Skill collection / shared catalog | Discover skills when no recognized manifest exists | Root marketplace.json |
plugin.json that does not declare a recognized agent-plugins $schema, missing component declarations can come from .claude-plugin/plugin.json; explicit root declarations win, and marketplace entry declarations fill remaining gaps.The order is defined in src/model/layouts.ts; selection and root-manifest fallback are implemented in src/catalog/manifests.ts.
The table says per layout whether this plugin reads a given surface at all. Yes means the layout's own files are read and injected; Partial means only part of the formats is understood, or the upstream layout has no such definition — the notes below say which. Evidence: the compatibility report and layout audit.
| Layout | Skills | Agents | Commands | MCP | Hooks | LSP |
|---|---|---|---|---|---|---|
| Claude Code | Yes | Yes | Yes | Yes | Partial | Yes |
| Codex | Yes | Yes | Yes | Partial | Partial | Yes |
| Cursor | Yes | Partial | Partial | Partial | No | Yes |
| Kimi Code | Yes | Yes | Yes | Yes | Partial | Partial |
ZCode .zcode-plugin/ | Yes | Yes | Yes | Yes | Partial | Partial |
Qoder CLI .qoder-plugin/ | Yes | Yes | Yes | Partial | Partial | Partial |
| GitHub Copilot CLI | Yes | Yes | Yes | Yes | Partial | Yes |
Universal compatibility layout .plugin/ | Yes | Yes | Yes | Yes | Partial | Yes |
| agent-plugins | Yes | Partial | Partial | Yes | Partial | Partial |
| Manifest-less skill collection | Yes | Yes | Yes | Yes | Partial | Partial |
| Project-native directories | Yes | Yes | Yes | Yes |
skills/ directory, including flat SKILL.md files.agents/*.md, commands/*.md). Cursor plugin commands accept .md, .mdc, .markdown and .txt. Codex and Kimi native agent/command formats (TOML, YAML) have no adapter yet.mcp.json and agent-plugins' strict mcp.json both work; Kimi Code is inline-only. Codex app connectors stay outside this adapter.afterFileEdit) are reported instead of simulated. Cursor's native events are not read..lsp.json / lsp.json locations. Declarations inside a project are reported but not mounted: the host LSP registry is global. Some layouts only expose LSP directories for preview..plugin/plugin.json location and a Vercel repository uses it, but no cross-vendor specification exists.Reading a layout does not guarantee every behavior of its original platform. Invalid declarations are diagnosed and skipped.
The plugin settings card has Scan project Agent layouts (dsh-agent-plugins-market.scanProjectLayouts, default off). It controls one thing: whether the project you are working in contributes skills, commands, agent roles, MCP servers and hooks from its own directories (.claude, .agents, .codex, .cursor, .kimi, .zcode, .qoder, .github). Turning it on adds those candidates; turning it off removes them on the next discovery pass. The card applies a switch when you save it, and each setting offers Use default while it carries your own value. Configured sources and installed suites are unaffected.
Project layouts lists the directories and files read per layout and how they are mounted.
The README repositories have offline snapshots in tests/fixtures/real-layouts/ with commit IDs, hashes and licenses, and each layout has an isolated reader test. The compatibility report records the sampled repositories, their schema verdicts and the scanner output; the audit records independent resource checks. These are documentation, source and sample checks — not end-to-end certification for every platform.
Review third-party suites before enabling them: enabled services and hooks can execute programs. See the runtime and security details.
Why is an installed skill or tool missing?
Check that the suite and the relevant capability are enabled. Skills may restrict manual invocation. MCP / LSP panels show user-service failures. Project resources additionally require the project-scan switch; unsupported native fields and project LSP declarations appear in scan diagnostics.
Where do I configure MCP tokens?
Open the service in MCP services. Missing environment references show needs-credentials. Host-managed credentials are write-only; launch-environment credentials require changing the environment and restarting DSH.
How do I add a service that no suite declares?
Use Add in MCP services or LSP servers. The declaration is validated, stored in ~/.agents/mcp.json or ~/.agents/lsp.json, and mounted through the same lifecycle as suite services. Host-observed services remain read-only.
Do sources refresh automatically?
Only when Background source updates is on: every configured source is then refreshed every 6 hours, starting one interval after you enable it. The switch is off by default, and the refresh button always works.
What if a source download fails?
Use a local directory, adopt a manual checkout, or configure a proxy / mirror. See source configuration.
When do local edits become visible?
There is no file watcher. Local-source discovery caches results for up to 30 seconds; refresh the source to invalidate them immediately. Project discovery has a separate five-second cache. A refresh does not happen automatically on an already-open page.
Does removing a source delete its files?
Only when you tick also delete the managed market directory in the confirmation. That removes the source's checkout under ~/.dsh/agent-plugins/.sources/<id> — including one you cloned yourself and adopted. A local-directory source pointing outside .sources/ is never deleted.
report_market_issue report through the gh CLI or a GitHub token; with neither, it opens a prefilled GitHub issue page and hands you the complete issue text.| Partial |
| No |