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-pre-push-checksgit 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-pre-push-checks)<a href="https://agentmods.dev/skills/sparkelf/deepseek-harness-plus/dsh-pre-push-checks"><img src="https://agentmods.dev/badge/skills/sparkelf/deepseek-harness-plus/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.
<a href="https://agentmods.dev/skills/sparkelf/deepseek-harness-plus/dsh-pre-push-checks"><img src="https://agentmods.dev/badge/skills/sparkelf/deepseek-harness-plus/dsh-pre-push-checks.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.00068 | $0.02086 |
| Opus 5 | $0.00034 | $0.01043 |
| Sonnet 5 | $0.00014 | $0.00417 |
| Haiku 4.5 | $0.00007 | $0.00209 |
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 3d 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.
This is a copy
94% identical to dsh-pre-push-checks — 0 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.
How it starts
The opening of the file, as written. The whole thing — 128 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
- Confirm the checkout and branch.
git status --short --branch
git rev-parse --show-toplevel
- 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.
When the outgoing change adds or changes a resource-owning or asynchronous test, fixture, helper, or CI execution path, use dsh-ci-test-reliability first to decide whether restoration, negative-control, quiescent-teardown, or concurrent-process evidence applies. This skill still selects the commands and avoids repeating evidence that already passed.
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.
- 3d ago Changed 37922ee9e6fd
- 6d ago Changed · +2 lines 566c2a111e4b
- 10d ago First seen · 126 lines · 68 tokens per session scan A b7e6698b0900
dsh-pre-push-checks is a skill published in the GitHub repository SparkElf/deepseek-harness-plus (2 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 2,086 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to dsh-pre-push-checks, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
qa-testing
Verify your work by actually operating the app or website you changed, instead of assuming it works. Strongly recommended whenever you build, modify, or debug a web app, website, or desktop GUI app. Drive real browsers with the agent-browser CLI and native desktop apps with the cua-driver CLI. These are installed on…
visual-acceptance
A visual final-review method for user-interface changes. It checks the rendered result with repeatable screenshots, pixel values, computed styles, and CSS layering checks across themes.
ultra-adlc
End-to-end delivery orchestration for explicitly requested, very large software changes that must be completely implemented and independently proven. Use when the user invokes "ultra-adlc" or asks for an Ultra-ADLC-scale full delivery; do not use for ordinary features, small fixes, reviews, or ad hoc parallel work.
remote-tests
Testing against remote executors in integration tests.
test-first
A test-first development guide, where tests are written before the code they check. TDD, or test-driven development, means first writing a test that fails, then writing the simplest code that makes it pass.
tdd
A test-driven development workflow based on repeating three stages: write a failing test, make it pass, then improve the code. The tests focus on what users can do through public interfaces rather than internal implementation details.