DeepSeek Harness is an open-source framework for building and running AI agents, organized so that its functionality is provided through plugins. Developers use it to launch agent workflows through a local web interface or from source, while the catalogue add-ons extend the harness as plugins.
Borrowing it
Nothing to install: this file belongs to deepseek-ai/deepseek-harness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/deepseek-ai/deepseek-harness/master/.agents/skills/dsh-create-upgrade-guide/SKILL.mdgit clone --depth 1 https://github.com/deepseek-ai/deepseek-harnessWrote 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/deepseek-ai/deepseek-harness/dsh-create-upgrade-guide)<a href="https://agentmods.dev/skills/deepseek-ai/deepseek-harness/dsh-create-upgrade-guide"><img src="https://agentmods.dev/badge/skills/deepseek-ai/deepseek-harness/dsh-create-upgrade-guide/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/deepseek-ai/deepseek-harness/dsh-create-upgrade-guide"><img src="https://agentmods.dev/badge/skills/deepseek-ai/deepseek-harness/dsh-create-upgrade-guide.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.00078 | $0.00855 |
| Opus 5.5 | $0.00031 | $0.00342 |
| Sonnet 5.5 | $0.00016 | $0.00171 |
| Haiku 4.5 | $0.00008 | $0.00085 |
Grade A, and why
dsh-create-upgrade-guide 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 16d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DSH Create Upgrade Guide
An upgrade guide tells a reader who runs release vT what to change to run the next release. Write it in the change that introduces the break, as soon as the break is recognized; do not defer it to release preparation.
Scope
Write a guide only for breaks that someone outside the repository can observe after upgrading:
dshcommands, flags, and profile names;cordis.yml, patch, overlay, and settings keys or their accepted values;- persisted user data: Session logs, SQLite stores, and user data directories;
- TypeScript and Python SDK exports, JSON-RPC, HTTP, and ACP messages;
- published package names and entry points.
Pre-stable internal APIs whose consumers are all updated in the same change need no guide. A Session-format change still follows type acknowledgements; its guide states only the reader's actions and links that record.
Location
docs/upgrade-guide/v<version>/<item>/guide.md
<version>is theversionfield of the rootpackage.jsonwhen you write the guide, for examplev0.1.7-rc.2. The guide describes the upgrade from that release to the next one.<item>is a kebab-case name of the changed surface, for exampleprofile-flag-rename.- Each item directory holds exactly
guide.md, its Chinese counterpartguide.zh.md, and the pairing recordguide.i18n.yaml: no index, no attachments.
Maintenance
While the root version is unchanged, the current version directory describes the delta from vT to current master. When a later change touches a surface a guide there covers, update that guide in the same change; delete the guide when the break is reverted. After the version bump, guides in older version directories are frozen; a new break goes into the new version directory. Never write a guide spanning more than one release.
Format
Start from the upgrade-guide template. verify-upgrade-guides enforces:
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.
- 16d ago First seen · 55 lines · 78 tokens per session scan A 0ee972372b3f
dsh-create-upgrade-guide is a skill published in the GitHub repository deepseek-ai/deepseek-harness (250,433 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 855 once invoked, about $0.0003 per session on Opus 5.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-09-30.
Other skills, from other repositories
manage-taskboard
Manage work in the native DeepSeek Harness Taskboard with exact task ids and optimistic versions. Use when an Agent must inspect project work, claim an eligible todo, record progress or blockers, verify an implementation, submit it for human review, or release its own claim; also use when a human asks how to accept…
industry-research-method
A Chinese-language method for researching an industry by mapping its supply chain, tracking policies and news, and writing sourced reports. It separates the chain into upstream inputs, midstream production, and downstream distribution or use.
company-research-method
A documented process for researching a company using supplied files and selected public sources. It produces a company overview with business details, sourced financial figures, and stated risks.
dsh-plugin-guide
Use when developing, reviewing, packaging, debugging, or answering questions about DeepSeek Harness (DSH) plugins — the plugin-based agent harness on vendored Cordis. Applies the official plugin-development constraints (plugin contract, cordis.yml layers, services/events/effects, tool DSL, bundles/profiles) backed by…
setup-matt-pocock-skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.