dsh-agent-plugins-market

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

Pages

Market Add sources, preview suites, install and enable.	Skills Browse skills and author your own.	Commands Manage prompt templates invoked as /name.
Agent personas Roles with an exact provider, model and effort.	MCP services Credentials, authorization and connection status.	LSP servers Language server configuration and runtime status.

What you can do

• Ten suite layouts. Claude Code, Codex, Cursor, Kimi Code, ZCode, Qoder CLI, GitHub Copilot CLI, Universal .plugin/, agent-plugins and manifest-less skill collections.
• Sources. Add a Git repository, a local directory or an archive (.zip / .tar.gz / .tgz / .tar); adopt a checkout you cloned yourself; refresh on demand; delete a managed checkout when you remove its source.
• Downloads that fit your network. Pick a download region — default 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.
• Runtime surfaces. Enabled suites inject into sessions: skills into the catalog and slash menu, commands as /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.
• MCP. A built-in bridge runs stdio, Streamable HTTP with OAuth and legacy SSE without a host MCP client. ${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. Self-provisioned: installing the plugin is the whole setup, and the 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.
• Agent personas and delegation. Role cards save an exact provider, model and reasoning effort; they appear in the session catalog and run through subagent_run, which starts a durable background child and returns its id immediately.
• Project dimension. Skills, agents, commands, MCP servers and hooks are read from the project's own directories with no install step.
• Your own resources. Author skills, commands and agent personas as Markdown under ~/.agents/, then edit them or disable them without deleting the files.
• Background source updates. Optionally refresh every configured source on a timer; off by default.
• Web workspace. Six tabs — Market, Skills, Commands, Agent personas, MCP services and LSP servers — each with search, filters and a grid/list toggle, plus status panels with diagnostics, credential editing, and an install confirmation that warns before executable third-party content is enabled.
• Bilingual interface and feedback. Workspace strings and injected prompts follow the host language. With feedback enabled, the model can file a 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.

Quick start

Install into your profile, replacing <name> with its name:

dsh plugin --profile <name> add dsh-agent-plugins-market

1. Restart DSH and open Settings → Agent Plugins Market.
2. In Market, add a source, for example https://github.com/anthropics/claude-plugins-official. No sources are preconfigured.
3. Open a suite, review its contents, then install it and ensure it is enabled.
4. For a suite with skills, check the Skills tab and type / 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.

Everyday use

The workspace has six tabs:

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.

Compatibility and boundaries

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:

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.

Layout detection precedence

When multiple manifests exist in the same suite directory, the first existing file in this order selects the layout:

• Manifests are tried in order: a manifest that cannot be read or validated is reported and the next one is tried, down to the fallback. If every candidate fails, the suite is diagnosed instead of loading half of it.
• Component fallback: for a root 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.
• Marketplace catalogs follow the same order: the first catalog that produces suites wins, and invalid or empty catalogs allow the next candidate to be tried.

The order is defined in src/model/layouts.ts; selection and root-manifest fallback are implemented in src/catalog/manifests.ts.

Layout support matrix

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.

• Skills are read from the paths a manifest declares and from the conventional skills/ directory, including flat SKILL.md files.
• Agents and commands are read as Markdown (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 covers declared files, inline tables and arrays. Cursor's schema-less mcp.json and agent-plugins' strict mcp.json both work; Kimi Code is inline-only. Codex app connectors stay outside this adapter.
• Hooks map the command-style events DSH has an equivalent for; events without one (for example afterFileEdit) are reported instead of simulated. Cursor's native events are not read.
• LSP accepts declared files, arrays and inline tables plus the conventional .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.
• agent-plugins standardizes portable skills and MCP only. Agents, commands and hooks for that layout are read through this plugin's shared directory conventions, not through the specification.
• Universal is a compatibility-layout label used by this plugin; the OpenHands SDK documents the same .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.

Project layout switch

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.

Verified samples

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.

FAQ

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.

More documentation

• Usage guide: installation, source configuration, storage, host requirements, project layouts, MCP / LSP and feedback settings.
• Plugin specifications: per-dialect reference schemas and evidence, plus the vendored agent-plugins v1.0.0 contracts.
• Compatibility report: one real repository per schema, with commits, schema verdicts and scanner output.
• Contributing: development setup, checks and PR workflow.
• Security policy · Release history · MIT license.
• Domain glossary · Architecture.
• Agent roles and storage: installed-resource editing, model routing and migration.