DeepSeek Harness Plugin Hub

发布与管理完整 Harness Profiles，发现适合你的插件。

探索

插件目录环境预设文档中心动态

社区

发布插件联系我们报告问题

相关链接

Plugin Hub GitHubDeepSeek Harness 官方项目系统状态隐私说明
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

独立、非官方社区项目，与 DeepSeek 官方无隶属、授权或背书关系。

Context Budget — DeepSeek Harness 插件（DSH Plugin）
DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录
← Plugins
C

@jidekaixin2dian/dsh-context-budget

Context Budget

在 DeepSeek Harness 中管理 MCP 服务器和技能，并隐藏下一次提示中的工具组，同时估算令牌成本。预算更改无需编辑配置或重启。

插件会安装到这里；不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add github:jidekaixin2dian/dsh-context-budget#66f4979018f95dac618f812dbf183a0498e49f1c
README兼容性版本

兼容性与来源证明

Context Budget 以 @jidekaixin2dian/dsh-context-budget 发布，当前版本为 0.3.1。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。

DSH 兼容范围
*
运行环境
web
发布来源
github
Registry 更新时间
2026/10/18

版本

0.1.1stable
2026/10/18
0.3.1stable
2026/10/18

相关插件

正在加载相关插件…

最新版
0.3.1
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
未提供
文件数
未提供
Surface
web
许可证
MIT
发布源
github
周下载
0
查看源码 ↗
README Badge

点击下方 Badge 复制 Markdown，粘贴到 README 即可。

这是你的 Plugin？认领权益 · 优先安全扫描

验证 package.json 声明的 GitHub 仓库，即可管理这个公开页面。认领后，Hub 会优先安排当前版本的安全扫描，并在通过后公开展示结果。

认领这个 Plugin →
报告问题

相关插件

继续浏览 integrations-communication 分类下经过校验的插件。

Acp App@deepseek-ai/dsh-acp-appdsh ACP 配置文件包：基于 dsh-base 的仅限自动化的 JSON-RPC stdio 和进程生命周期管理Experimental Plugin Market Bundle@deepseek-ai/dsh-experimental-plugin-market-bundle实验性自定义插件市场：用于浏览和安装来自插件市场索引的捆绑包的“发现”选项卡Workbuddy Connectdsh-workbuddy-connect将 WorkBuddy 桌面 App 中包含的模型自动接入 DeepSeek Harness，无需配置。Ab Wechat Scrapedsh-ab-wechat-scrape--- description: "树外 wechat_scrape 工具：获取微信公众号文章，过滤推广区块，并将每篇文章保存为 Markdown 文件，供此机器的 dsh 配置文件维护者使用。" kind: "package-reference" ---

README

dsh-context-budget

Manage MCP servers and toggle skills in DeepSeek Harness — and hide tool groups from the next prompt with token-cost estimates. Budget changes need no config edit, no restart and no MCP process churn; MCP server edits write the normal patch file and apply through HMR.

Context budget

Why

Every MCP tool is sent as a full JSON Schema on every request. A server with dozens of tools can quietly consume more context than the conversation itself. Configuration managers can add, remove or toggle servers, but the prompt is still paid on the next turn.

This plugin manages three things in one page:

  • MCP servers — list, add, edit, remove, enable/disable; writes the profile/global cordis.patch.yml and lets HMR apply it.
  • Skills — search, create, delete, and enable/disable one skill through a rank-0 override provider.
  • Prompt budget — group the effective tools by MCP server, hide a whole group, see the approximate cost, and restore it without restarting the MCP process.

Install

From GitHub (no build step; lib/ is included):

dsh plugin --profile <your-profile> add github:jidekaixin2dian/dsh-context-budget

For the official desktop app, install through its plugin manager if it manages the profile for you. Restart DSH once after installing the host half, then hard-refresh the web UI.

Use

Open Settings → Context budget:

  • Context budget tab:
    • All visible — clear every override;
    • Hide all MCP — one switch for every mcp__<server>__* group;
    • Hide largest group — the group with the biggest schema cost;
    • Lean — MCP + Skill + memory + schedule off;
    • per-server MCP rows, Skill catalog, memory tools, schedule tools.
  • MCP servers tab: add/edit/remove, enable/disable; stdio command/args/env or streamable-http URL/headers.
  • Skills tab: search, create/delete user or project skills, and toggle individual skills.

A read-only Core tools row is always kept.

Model tool:

context_budget action=status
context_budget action=session disabled=["mcp:github", "skills"]
context_budget action=reset

mcp is a wildcard for all MCP servers; mcp:<server> targets one. The global budget applies to every session and subagent; action=session only overrides the current session.

How it works

The budget half applies ctx.tools.restrict({ deny }) on the agent scope during agent/pre-step. The tool schemas are removed from prompt assembly before the request is sent. It listens to tools/change, agent/created and agent/status so dynamic MCP additions and subagents get the restriction too.

The MCP tab edits the profile/global cordis.patch.yml line by line (unrelated rows and comments survive); DSH HMR applies the changed MCP row. The Skill tab registers a rank-0 override provider with modelInvocable:false for disabled names.

Token numbers are estimates from the serialized JSON schemas plus Skill catalog descriptions, not a provider tokenizer.

Compatibility

  • Dynamic MCP managers that register tools in the agent scope (for example lazy MCP loading) are respected: their tools are shown in the scoped count, but ctx.tools.restrict cannot hide scoped registrations. Use that manager's own unload.
  • Other MCP/Skills managers own their own rows and files; this plugin edits only @deepseek-ai/dsh-mcp-client rows it manages and its own skill override. tools/change picks up their changes.
  • dsh-context reads request headers; hiding tools here reduces its tool-schema row and the actual prompt together.

Limits

  • MCP processes stay alive when only the budget is used; this saves prompt tokens, not RAM.
  • MCP CRUD writes cordis.patch.yml; DSH HMR applies it. Review the diff if you hand-edited the file.
  • Skill toggles use the global skill registry; a skill discovered only in a scoped provider may not be hidable.
  • Skill file import from ZIP/folder is not implemented; create writes ~/.dsh/skills/<name>/SKILL.md or <cwd>/.dsh/skills/<name>/SKILL.md, delete moves to .trash.
  • Tool descriptions/schemas must be known before a restriction can be computed; a first request may calibrate the full baseline.
  • Host-half updates need a DSH restart; client-half updates need a hard refresh.

Development

npm test

Pure grouping rules are in lib/groups.js; the host and browser halves are hand-written ESM/CJS to keep the package dependency-free.

MIT.