dsh-web is a plugin ecosystem that adds a web interface and optional tools to DeepSeek Harness, an AI development environment. It is used to provide features such as task boards, mobile remote control, SSH operations, image understanding, file and code panels, Git views, agent presets, and interchangeable skins through independently loaded plugins. The catalogue skills are plugins and related workflows for extending and operating the DSH Web environment.
Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/zhu1090093659/dsh-web/dsh-web-release)<a href="https://agentmods.dev/skills/zhu1090093659/dsh-web/dsh-web-release"><img src="https://agentmods.dev/badge/skills/zhu1090093659/dsh-web/dsh-web-release/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/zhu1090093659/dsh-web/dsh-web-release"><img src="https://agentmods.dev/badge/skills/zhu1090093659/dsh-web/dsh-web-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00151 | $0.06254 |
| Opus 5 | $0.00076 | $0.03127 |
| Sonnet 5 | $0.00030 | $0.01251 |
| Haiku 4.5 | $0.00015 | $0.00625 |
Grade A, and why
dsh-web-release scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dsh-web 发布（release / publish）
本技能固化 dsh-web 全家桶的完整发版流程：全仓统一版本 → 提交 → 打 tag → 推送触发 GitHub Actions 发布管线（构建/测试/npm 发布/GitHub Release）→ 发布后验证。
仓库事实（先读，决定每一步怎么做）
- 仓库：zhu1090093659/dsh-web（PUBLIC），本机路径 /Users/zcl/code/dsh-web。
- 全家桶由
scripts/lib/family-packages.mjs非递归遍历packages/与packages/skins/得到；当前工作树为 19 个家族包（packages/*18 个 +packages/skins/skin-center1 个），@linxin666/dsh-client-ui-skin-center也是独立发布包。版本与包数量以node scripts/verify-version.mjs X.Y.Z的输出为准，不在技能中手抄固定数量。 全部发布到 npm scope@linxin666，registry 固定 registry.npmjs.org。 - 版本策略：全仓统一版本（tag vX.Y.Z = 每个 package.json 的 version，由管线强制校验）。
- 未指定具体版本号时：不追问版本号；以远端最新且已发布的正式
vX.Y.Ztag 为上一版本， 默认目标为下一个补丁版本X.Y.(Z+1)。用户明确给出版本号，或明确要求 major/minor/prerelease 变更时，按该要求执行；远端 tag 与 npm 已发布版本不一致时，按下方失败恢复规则处理，不自行猜测。 - npm 不允许重复发布同一版本号：已发布过的版本号（如 0.1.3/0.1.4/0.1.5）不可重发， 只能 bump 到下一个版本。
- 发布通道：npm 发布全部由 GitHub Actions 管线完成，使用仓库 secret
NPM_TOKEN（npm automation token，@linxin666 scope）；本机 npm 登录态不固定（无登录态时npm whoami401 属正常；本机当前以 linxin666 登录），发版不依赖本机登录态。 - npm 通道已恢复（2026-08-31 起）：release.yml 的 workflow env
NPM_PUBLISH_ENABLED: 'true'；发布管线执行完整门禁、版本校验后运行pnpm -r publish --tag latest与 legacy 双发（均以该开关门控），发布后立即用scripts/verify-registry.mjs断言每个家族包的 tag 版本都能从 registry 解析 （带重试预算，覆盖 npm 传播延迟）。开关曾因家族跟踪未上 npm 的@deepseek-ai/*alpha cohort 而被暂停（决策记录.agents/notes/implemented/process/2026-08-28-pause-release-npm-publish-unstable-dsh-alpha.md， 恢复记录.agents/notes/implemented/process/2026-08-30-restore-npm-publish-alpha.2.md）。 若将来 cohort 再次无法从 registry 解析，把开关改回'false'，tag 推送即退回 GitHub-Release-only（此时 mount smoke 的 auto 模式以 workspace 打包的 file: tarball 验证本 tag 构建）。 - 根 package.json 是 private（不发布）；
pnpm -r publish自动跳过。 - 分支模型：
dev是开发分支（集成分支），本地开发与远程 PR 统一以dev为目标（远端默认分支）；main是稳定分支（发布分支），只接收dev上测试通过后合入的代码，发版 tag 一律从main打。dev/main均已启用分支保护（要求 PR + CI 全绿；管理员可绕过，维护者直推 仍可用，功能改动仍须先经dev）。 - 仓库禁 emoji（所有文件含提交信息与 tag 信息）；CI 会校验。
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago Changed · +1 lines 22fd94cbd14d
- 7d ago Changed · +6 lines 4892d6601e28
- 12d ago Changed · +1 lines 88c1a360a0d0
- 12d ago First seen · 266 lines · 151 tokens per session scan A 9ea497e4d2cd
dsh-web-release is a skill published in the GitHub repository zhu1090093659/dsh-web (7,417 stars, last pushed today), licensed Apache-2.0. It adds 151 tokens to every session and 6,254 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
market-release
A release workflow for publishing a new version of a software package. It uses release-please to create a release pull request, then creates a tag, a GitHub release, and an npm publication after the pull request is merged.
release-deploy
A release and deployment skill for preparing a software project for GitHub publication and putting it online.
git-workflow
Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes. Use when choosing a branching strategy, writing commit conventions, deciding merge versus rebase, or resolving conflicts.
github-ops
GitHub repository operations, automation, and management. Issue triage, PR management, CI/CD operations, release management, and security monitoring using the gh CLI. Use when the user wants to manage GitHub issues, PRs, CI status, releases, contributors, stale items, or any GitHub operational task beyond simple git…
opensource-pipeline
Open-source pipeline: fork, sanitize, and package private projects for safe public release. Chains 3 agents (forker, sanitizer, packager). Triggers: '/opensource', 'open source this', 'make this public', 'prepare for open source'. Use when a private project must be forked, stripped of secrets, and packaged for public…
resolving-merge-conflicts
Use when you need to resolve an in-progress git merge/rebase conflict.