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.
Borrowing it
Nothing to install: this file belongs to zhu1090093659/dsh-web. 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/zhu1090093659/dsh-web/dev/.agents/skills/dsh-web-pre-push-checks/SKILL.mdgit clone --depth 1 https://github.com/zhu1090093659/dsh-webWrote 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-pre-push-checks)<a href="https://agentmods.dev/skills/zhu1090093659/dsh-web/dsh-web-pre-push-checks"><img src="https://agentmods.dev/badge/skills/zhu1090093659/dsh-web/dsh-web-pre-push-checks/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-pre-push-checks"><img src="https://agentmods.dev/badge/skills/zhu1090093659/dsh-web/dsh-web-pre-push-checks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00753 |
| Opus 5 | $0.00023 | $0.00377 |
| Sonnet 5 | $0.00009 | $0.00151 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
dsh-web-pre-push-checks 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 10d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dsh-web Pre-Push Checks
Run checks from the repository root after the implementation is stable. This workflow supplements AGENTS.md; it does not replace a focused regression test for changed behavior.
Inspect the outgoing change
- Confirm the branch, repository root, and worktree status.
- Inspect the requested base-to-head diff and every dirty file that will be included.
- Run
git diff --checkbefore reporting success. Do not stage unrelated changes withgit add -A. - Sync collaborator merges before validating:
git fetch originand rebase ontoorigin/dev(git rebase origin/dev). Aa728848 merges renderer / Wallpaper Engine / WebGL PRs intodev; when the rebase pulls in new base commits, re-run the affected gates on the rebased tree before reporting. - Verify the push target before pushing:
git remote -vmust resolve both fetch and push togithub.com/zhu1090093659/dsh-web, with noremote.origin.pushurloverride. A leftover push-URL redirect (e.g. from contributor-fork PR work) silently targets the wrong repository; restore withgit remote set-url origin https://github.com/zhu1090093659/dsh-webandgit config --unset remote.origin.pushurl. Push to contributor forks only via a named one-off remote (git remote add <name> <fork-url>) or a direct URL.scripts/git-pre-push-guard.sh(installed as.git/hooks/pre-pushper AGENTS.md) blocks a mispointed origin; keep it installed.
Required repository gates
Before a push or review claim, run the repository baseline unless a higher-priority instruction narrows the operation:
pnpm typecheck
pnpm test
pnpm test:scripts
pnpm docs:check
Run the narrowest owning test first for a behavior change. Add an affected-package build or pnpm build when package exports, manifests, runtime entry points, generated bundles, or build configuration changed.
Add checks dictated by the diff
shared/changes: runpnpm sync-sharedfollowed bypnpm sync-shared:check.- Aggregate membership or package additions/removals: regenerate with
node scripts/aggregate.mjs, then runpnpm aggregate:check. - Skin assets, skin registry, or market asset changes: run
pnpm market:checkandpnpm skin-center:check. - Community plugin index changes: regenerate with
node scripts/community-index, then runpnpm community:check. - Browser runtime imports, dependency manifests, or client bundle changes: run
pnpm runtime-deps:checkand the affected package build. - Changed package README files: update the paired language and record the pair through
pnpm docs:write-pairbeforepnpm docs:check. - User-facing client changes: follow dsh-web-web-qa and retain the actual GUI evidence.
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.
- 10d ago Changed · +1 lines cd6ac8500c19
- 12d ago First seen · 43 lines · 45 tokens per session scan A 979744366114
dsh-web-pre-push-checks is a skill published in the GitHub repository zhu1090093659/dsh-web (7,417 stars, last pushed today), licensed Apache-2.0. It adds 45 tokens to every session and 753 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-08-30.
Other skills, from other repositories
resolving-merge-conflicts
Use when you need to resolve an in-progress git merge/rebase conflict.
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…
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.
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.
commit-message
Guidance for writing Git commit messages using Conventional Commits, a common format such as fix, feat, or docs followed by a short description. It focuses on explaining why a change was made.
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…