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-plugin-ownership-and-distributiongit 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-plugin-ownership-and-distribution)<a href="https://agentmods.dev/skills/sparkelf/deepseek-harness-plus/dsh-plugin-ownership-and-distribution"><img src="https://agentmods.dev/badge/skills/sparkelf/deepseek-harness-plus/dsh-plugin-ownership-and-distribution/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-plugin-ownership-and-distribution"><img src="https://agentmods.dev/badge/skills/sparkelf/deepseek-harness-plus/dsh-plugin-ownership-and-distribution.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.00058 | $0.01058 |
| Opus 5.5 | $0.00023 | $0.00423 |
| Sonnet 5.5 | $0.00012 | $0.00212 |
| Haiku 4.5 | $0.00006 | $0.00106 |
Grade A, and why
dsh-plugin-ownership-and-distribution 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 1mo 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DSH Plugin Ownership And Distribution
Use this workflow before implementation whenever a capability may become a package, move between repositories, publish to npm, contribute Host or Client behavior, or enter a shipped profile. The owning decision is plugin ownership and distribution.
Required Evidence
Read the capability's current Host and Client entries, package manifest, bundle patch, settings and persistence owners, public Harness APIs, release workflow, and every profile that mounts it. For a third-party candidate, also report its repository, license, maintained version, feature fit, and unresolved compatibility risks. Do not install, move, or publish before the owner accepts the classification.
Read what the current owner also provides before deciding to replace it. A registry exposes the id it matches; it does not announce the capabilities that ride on the same implementation. A file-viewer registration reads as an extension point while the builtin it displaces may be the only editor for that file type, so replacing it silently drops editing, saving, and its settings. Name the replacement's owned surface — rendering, mutation, persistence, settings, disposal — and reject an option that drops any of it.
Name the delivery mechanism as one of four, never as "a patch". Profile configuration; our own plugin mounted on a published extension point; an npm-target patch on an external package, delivered through the profile's patchedDependencies; and a republished first-party package delivered through overrides. The first two travel as code we own; the last two are two different mechanisms for two different package populations — an external npm package is patched in place, while an official @deepseek-ai/* workspace whose built lib/ cannot express the change is repackaged under our scope. Deciding for one population does not decide for the other.
Decide Four Dimensions Separately
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · +4 lines · +13 tokens per session 8843bfef537b
- 2mo ago First seen · 58 lines · 45 tokens per session scan A a91857cd4253
dsh-plugin-ownership-and-distribution is a skill published in the GitHub repository SparkElf/deepseek-harness-plus (1 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 1,058 once invoked, about $0.0002 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-04.
Other skills, from other repositories
dsh-tui-guide
Use when the user asks about dsh-tui itself (usage, shortcuts, config, themes, migration, VS Code). Load before answering; skip for normal coding tasks.
review-changes
Review local code changes for concrete correctness, regression, security, and test gaps before shipping.
systematic-debugging
Diagnose failures from runtime evidence before editing code.
verify-before-done
Require fresh evidence before claiming an implementation, fix, build, or test is complete.
browser-use-cli
Drive a real browser from the shell with the browser-use CLI when a task needs page interaction, rendered DOM, or a logged-in session.
plugin-creator
Create and scaffold plugin directories for Codex with a required .codex-plugin/plugin.json, optional plugin folders/files, valid manifest defaults, and personal-marketplace entries by default. Use when Codex needs to create a new personal plugin, add optional plugin structure, generate or update marketplace entries…