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.00045 | $0.00810 |
| Opus 5 | $0.00023 | $0.00405 |
| Sonnet 5 | $0.00009 | $0.00162 |
| Haiku 4.5 | $0.00005 | $0.00081 |
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 7d 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 — 58 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.
Decide Four Dimensions Separately
| Dimension | Question |
|---|---|
| Plugin boundary | Does one Cordis plugin lifecycle own the capability's registrations and disposal? |
| npm publication | Must a versioned artifact resolve outside the source workspace? |
| Repository ownership | Which project owns compatibility, security, release, and retirement? |
| Default composition | Which shipped profiles mount the package without a separate user choice? |
Never infer one answer from another. A first-party workspace package may publish to npm; an external npm plugin may be default-mounted by a distribution; neither fact changes its source owner.
Ownership Closure
Identify one capability owner. That owner must carry every capability-specific Host entry, Client entry, settings UI, configuration schema, routes, migrations, install and uninstall behavior, and user documentation. Cross-repository adapters are allowed only for a real public protocol, error, trust, or lifecycle difference. A host-repository wrapper that merely registers UI for an external capability is forbidden.
An external plugin is admissible only when all of these are true:
- It uses published Harness extension points and imports no private host source.
- Its
dsh.bundlemounts the Host half and itsdsh.clientloads the browser half when present. - Installation, disable, upgrade, and removal cover every owned registration and artifact.
- Supported Harness versions are expressible through package metadata and documented public contracts.
- A named maintainer owns releases, compatibility, security fixes, and retirement.
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.
- 7d 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 (2 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 810 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
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.
codex-sync
Operate dsh-codex-sync from this session — preview and import Codex chats, toggle Skills/MCP/import settings, check MCP mirror health, install the reverse MCP bridge.
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.
python-debugging
Use this skill when fixing failing Python tests.