deepseek-harness-desktop: Skill for Codex

.agents/skills/dsh-pre-push-checks/SKILL.md

dsh-pre-push-checks is a skill for Codex from RZX00/deepseek-harness-desktop. It costs 68 tokens per session (1,608 once invoked), scanned A, a copy of dsh-pre-push-checks, MIT.

A checklist for validating changes in the DeepSeek Harness repository before pushing them to a shared Git branch. Git is a tool for tracking code changes, and a branch is a separate line of work.

In plain words
What is it for?
Use it before pushing, force-pushing, or marking work ready for review to inspect the branch, compare the full change scope, and run the relevant type checks and tests.
Why use it?
It helps select checks that match the files being changed and avoids claiming a change is ready without local evidence. It also covers rewritten branches after stack synchronization.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents).

This is RZX00/deepseek-harness-desktop's own configuration. It tells Codex how to work on deepseek-harness-desktop itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything deepseek-harness-desktop configures →

Reuse

Borrowing it

Nothing to install: this file belongs to RZX00/deepseek-harness-desktop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/RZX00/deepseek-harness-desktop/master/.agents/skills/dsh-pre-push-checks/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/RZX00/deepseek-harness-desktop

Made for: Codex.

Wrote 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.

agentmods badge for dsh-pre-push-checks

README.md
[![agentmods](https://agentmods.dev/badge/skills/rzx00/deepseek-harness-desktop/dsh-pre-push-checks/github.svg)](https://agentmods.dev/skills/rzx00/deepseek-harness-desktop/dsh-pre-push-checks)
Your own site
<a href="https://agentmods.dev/skills/rzx00/deepseek-harness-desktop/dsh-pre-push-checks"><img src="https://agentmods.dev/badge/skills/rzx00/deepseek-harness-desktop/dsh-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.

agentmods 80×15 button for dsh-pre-push-checks

Your own site · 80×15
<a href="https://agentmods.dev/skills/rzx00/deepseek-harness-desktop/dsh-pre-push-checks"><img src="https://agentmods.dev/badge/skills/rzx00/deepseek-harness-desktop/dsh-pre-push-checks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,608 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 86% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00068 $0.01608
Opus 5 $0.00034 $0.00804
Sonnet 5 $0.00014 $0.00322
Haiku 4.5 $0.00007 $0.00161

Measured 12d ago against content hash 8d2120972d88, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

dsh-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 12d 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.

Origin

This is a copy

86% identical to dsh-pre-push-checks — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/dsh-pre-push-checks/SKILL.md · 116 lines

How it starts

The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.

DSH Pre-Push Checks

Use this skill to run relevant local evidence once before a deepseek-harness push. The sole ordering exception is gh stack sync, which may publish a cascading rebase before the rewritten layers can be validated; validate them immediately afterward and do not merge until the evidence passes. Git hooks are intentionally narrow: pre-commit fixes staged lint, checks staged whitespace, and guards vendored-source metadata; pre-push runs only the incremental repository typecheck. CI owns exhaustive coverage and the platform matrix.

Inspect the outgoing change

  1. Confirm the checkout and branch.
git status --short --branch
git rev-parse --show-toplevel
  1. Verify the live PR base or stack parent, fetch that ref, and inspect the complete scope against it.
pnpm --silent run change-scope --base <verified-base-ref>

The command never guesses or fetches a base. Supply the ref verified from current remote or stack state; use --head <ref> when inspecting a commit other than HEAD. Its versioned JSON records committed paths relative to the resolved merge base, while staged, unstaged, and untracked paths describe the current worktree. After merging a changed base, rerun the report, reassess which behavior the combined scope can affect, and rerun only checks invalidated by the merge.

Select relevant evidence

There is no universal local baseline beyond the hooks. Every behavior change needs the narrowest available test or purpose-built check that would fail for its regression; add broader checks only for surfaces the diff actually reaches.

  • Package or script behavior: run the owning Vitest file or focused test name. Add adjacent package tests when a shared contract changes; leave repository-wide coverage to CI unless the change is genuinely cross-cutting or the user requests it.
  • Documentation, Agent Notes, catalogs, or doc-linked comments: run pnpm run doc-sync; run full lint when the documentation workflow requires it.
  • Model-, editor-, CLI-, or terminal-visible output: run the focused keyless snapshot or real runnable-example scenario that owns the output.
  • Package manifests, public exports, build configuration, worker/bin entries, or built runtime paths: run pnpm run build, the relevant hygiene checks, and the owning built-artifact smoke.
  • Real provider or agent behavior: run the relevant pnpm run test:e2e target when credentials are available; never print secrets.

Read the full file on GitHub · 116 lines

Files

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.

Changes

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.

  1. 12d ago First seen · 116 lines · 68 tokens per session scan A 8d2120972d88

Subscribe to this mod's changes

dsh-pre-push-checks is a skill published in the GitHub repository RZX00/deepseek-harness-desktop (10 stars, last pushed 28d ago), licensed MIT. It adds 68 tokens to every session and 1,608 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to dsh-pre-push-checks, differing in 12 lines, and is treated as a copy.

Related

Other skills, from other repositories

prowler-commit

Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 33 tokens

gh-auth-isolation

Safely manage multiple GitHub identities (EMU + personal) in agent workflows.

github/gh-aw · 20 tokens

comet-github

A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.

rpamis/comet · 72 tokens

github-skill

Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.

zeenie-ai/OpenCompany · 51 tokens

changelog-composer

Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".

Mathews-Tom/armory · 67 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens