An Apache-2.0 Cordis plugin that lets DeepSeek Harness (dsh) operators cap context usage by tiering MCP tools and skills as Exposed / Progressive / Blocked, discovered and invoked via `meta_search` / `meta_invoke`.
DSH integration
Native runtime
Author-claimed
Safety audit
Unaudited
Last verified
2026-08-30
License
Apache-2.0
01What can it help you accomplish?
Manage the exposure level (context footprint) and execution mode of MCP tools & skills in DeepSeek Harness through Exposed / Progressive / Blocked tiers.
A unified capability catalog (`ctx.meta`) plus two meta-tools — `meta_search` (discover Tool/Skill) and `meta_invoke` (execute tool / load skill) — so the model pulls capabilities on demand instead of loading everything into one request.
DeepSeek Harness (dsh) operators running many MCP tools/skills who want to cap token and context usage per request without forking upstream.
Review and tune the three-tier capability policy from the DeepSeek Harness settings UI.
A 'Capability Menu' tab (Settings / General) listing MCP tools (grouped by server, collapsible) and Skills with tri-state dots and per-tier counts; switch a capability's tier with one click and changes apply live, no restart.
Operators and admins who prefer a GUI over editing the YAML policy file by hand.
02How to install into DeepSeek Harness
Prerequisites
- Node.js installed
- dsh CLI installed (`dsh plugin` forwards to pnpm internally)
Installation steps
- 01
$ dsh plugin --profile web add @daweifu/capability-menu
- 02
$ dsh plugin --profile web add @daweifu/capability-menu-web
Verify the integration
- Run `dsh --profile web --dump-config | grep -E 'capability-menu'` — the README says you should see this package's own patch layer (capability-menu-registry / -search / -invoke / -policy).
Rollback
- dsh plugin --profile web remove @daweifu/capability-menu
- dsh plugin --profile web remove @daweifu/capability-menu-web
03DSH integration and capability boundaries
Installed as a Cordis plugin via the dsh CLI (`dsh plugin --profile web add @daweifu/capability-menu`) and runs inside the DeepSeek Harness runtime; exposes `ctx.meta`, `meta_search` and `meta_invoke` without forking upstream.
Unified capability catalog (ctx.meta)
MCP tools and skills registered in the DeepSeek Harness runtime→a single capability directory (`ctx.meta`) indexed by `ctx.tools` / `ctx.skills`
does not modify upstream source — combines into the same runtime via the Cordis plugin mechanismTwo meta-tools: meta_search & meta_invoke
a capability query or invocation request from the model→`meta_search` lists/details capabilities (Tool/Skill); `meta_invoke` executes tools through the full `ctx.tools` pipeline or loads skill bodies
`meta_invoke` performs real tool execution; blocked tools are rejectedprogressive tools/skills stay out of context until invokedExposed / Progressive / Blocked three-tier policy
a policy config of tools/skills exposed / progressive / blocked rules→controls what the model sees per request (full schema vs catalog-only vs hidden) and how each capability executes
progressive tools/skills are removed from the model's context payload until invokedblocked tools are rejected by meta_invoke
04Who is it for? When not to use it?
Good for
- DeepSeek Harness (dsh) operators running many MCP tools/skills who want to cap token and context usage per request without forking upstream.
- Operators and admins who prefer a GUI over editing the YAML policy file by hand.
Not for
- Native (non-`mcp__`) tools such as `bash` / `read` / `write` / `edit` / `read_image` / `glob` / `grep` are NOT cataloged by the plugin — they are not indexed by `meta_search`, not dispatched by `meta_invoke`, and do not appear in the capability list. They only keep model visibility by being listed in `tools.exposed`.
- The meta-tools `meta_search` / `meta_invoke` are always Exposed and cannot be blocked; listing either in `blocked` fails loud (the policy errors out).
05Compatibility, maintenance and safety notes
- Native (non-`mcp__`) tools such as `bash` / `read` / `write` / `edit` / `read_image` / `glob` / `grep` are NOT cataloged by the plugin — they are not indexed by `meta_search`, not dispatched by `meta_invoke`, and do not appear in the capability list. They only keep model visibility by being listed in `tools.exposed`.
- The meta-tools `meta_search` / `meta_invoke` are always Exposed and cannot be blocked; listing either in `blocked` fails loud (the policy errors out).
Apache-2.0; no tagged release yet (latest_release is null); last push 2026-08-25; repo created 2026-08-19
06Frequently asked questions
How do I install dsh-capability-menu with the dsh CLI?
Make sure Node.js and the dsh CLI are installed, then run `dsh plugin --profile web add @daweifu/capability-menu` and `dsh plugin --profile web add @daweifu/capability-menu-web` for the server and the Capability Menu tab. Inside, `dsh plugin` forwards to pnpm.
How does it connect to DeepSeek Harness?
It's a Cordis plugin that combines into the same runtime as the Harness via the Cordis plugin mechanism — it does not fork upstream. It adds a unified capability catalog (`ctx.meta`) and two meta-tools (`meta_search` / `meta_invoke`).
What are the Exposed / Progressive / Blocked tiers?
Exposed = full schema stays in the model's context, called directly. Progressive = kept out of context (zero cost) and pulled via `meta_search`/`meta_invoke` only when used. Blocked = hidden from discovery and refused by `meta_invoke`. It's a config you set, not an auto-count.
How do I verify the install worked?
Run `dsh --profile web --dump-config | grep -E 'capability-menu'` — the README says you should see this package's own patch layer (capability-menu-registry / -search / -invoke / -policy).
How do I roll back / uninstall?
Remove both packages with `dsh plugin --profile web remove @daweifu/capability-menu` and `dsh plugin --profile web remove @daweifu/capability-menu-web`.
07Related DSH workflows
dsh-routing-suite
by yjh051108
dsh-routing-suite — injector + router-standard kit: install the runtime injector first, then the task-aware reasoning-mode router preset (measured P1-P23).
brooks-lint
by hyhmrright
AI code reviews grounded in 12 classic engineering books — decay risk diagnostics with book citations, severity labels, and 6 analysis modes including full-sweep auto-fix
oh-dsh
by hust-open-atom-club
Community distribution: TUI, desktop, and Web UI as one bundle with layered installation.
perfect-web-clone
by ericshang98
Pixel-perfect clones of any webpage. Paste a URL, get a measured Vite + React replica.
08Data and sources
为 [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) 提供统一的能力目录（`ctx.meta`）、两个元工具（`meta_search` / `meta_…
它不修改上游源码，通过 Cordis 插件机制与 Harness 组合进同一个运行时
This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-08-30. Found an error? Submit a correction.
Best DeepSeek Harness Plugins
Twelve plugins worth installing first — picked from the whole catalog, across every category.