Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add SparkElf/deepseek-harness-plus --skill dsh-promote-deploymentgit clone --depth 1 https://github.com/SparkElf/deepseek-harness-plusWrote 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/sparkelf/deepseek-harness-plus/dsh-promote-deployment)<a href="https://agentmods.dev/skills/sparkelf/deepseek-harness-plus/dsh-promote-deployment"><img src="https://agentmods.dev/badge/skills/sparkelf/deepseek-harness-plus/dsh-promote-deployment/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/sparkelf/deepseek-harness-plus/dsh-promote-deployment"><img src="https://agentmods.dev/badge/skills/sparkelf/deepseek-harness-plus/dsh-promote-deployment.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.00072 | $0.02567 |
| Opus 5.5 | $0.00029 | $0.01027 |
| Sonnet 5.5 | $0.00014 | $0.00513 |
| Haiku 4.5 | $0.00007 | $0.00257 |
Grade A, and why
dsh-promote-deployment scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s https://registry.npmjs.org/<encoded-name> | grep -c '"<version>"' How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DSH Deployment Promotion
Use this skill to move a running deployment onto a new release. The deployment is not the repository checkout: it is a release mirror under the DSH home, with its own sources, build outputs, and profile. Changing a version in the profile does not change what the runtime executes.
Find the tools before writing any step
The deployment already owns this procedure. Read these before running anything, and call them rather than re-deriving their contents:
| Command | Owns |
|---|---|
dsh-plus-build <mirror> |
pnpm install twice (a patch that adds a dependency changes the graph, and only a second install links it), then pnpm run build --profile official, then verify the brand record and that no workspace with dependencies lacks node_modules. |
dsh-plus-switch |
Move the served release to another mirror, tracking phases. |
dsh-plus-refresh rebuild | accept | restart | all |
Rebuild the mirror, record the profile as accepted, restart, or all three in that order. |
dsh-plus-mirror create --tag <official-tag> --mirror <path> --runtime <version> |
Extract an official tag into a fresh mirror, apply this repository's reviewed patches, typecheck them, regenerate the standalone manifests, build, create the profile, write the compatibility exemptions, relink the scope, and repair shadowed packages. dsh-plus-mirror check --mirror <path> reports the scope verdict. |
dsh-plus-exemptions --runtime <version> [--out <path>] |
Derive the profile's compatibility.json: every plugin whose published peer ranges cannot match the runtime. |
repair-shadowed-scope.mjs --release <mirror> |
Replace real directories that shadow a release package with links to its source. |
dsh-3080-restart |
Restart through the supervisor: repair profile scope, prove module uniqueness, re-accept the fingerprint, restart, then verify the client modules and the connection surface. |
relink-release.mjs --release <mirror> |
Restore the @deepseek-ai scope links a pnpm install inside the mirror rewrote. |
check-profile-scope.mjs --release <mirror> |
Report duplicate @deepseek-ai packages and unresolvable dependencies; both break every tool call while HTTP stays 200. |
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.
- 8d ago Changed · +21 lines d9f3b74532aa
- 10d ago Changed · +23 lines c5237791d66c
- 13d ago First seen · 77 lines · 72 tokens per session scan A 0fd818be8a15
dsh-promote-deployment is a skill published in the GitHub repository SparkElf/deepseek-harness-plus (1 stars, last pushed yesterday), licensed MIT. It adds 72 tokens to every session and 2,567 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-25.
Other skills, from other repositories
update-v8-version
Update Codex's pinned v8 / rustyv8 versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update rustyv8 artifacts, prepare or validate a V8 release candidate, check v8-canary, or diagnose why a V8 version update no longer builds.
release-notes
Write release notes for a tagged release — a business-impact summary of what changed for the user, plus a thanks section naming every contributor whose commits are in the release. Short by construction.
ship
Use when code is ready to ship — creates PRs, merges, deploys, and verifies. Handles the full PR-to-production pipeline. Triggers on /ship.
changelog
Create engaging changelogs for recent merges to main branch.
npm
Publish and manage packages on the npm registry (npmjs.com), publish, dist-tags, deprecate, owners, download stats, private installs. Use when the user asks to publish, release or manage an npm package, or to inspect the registry.
release-verification
A release-verification checklist for software versions and packages. It covers changelogs, tests, packaging, installation smoke checks, version-control actions, publishing, and checks after release.