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 EthanYoQ/Skill-hub --skill dsh-pre-push-checksgit clone --depth 1 https://github.com/EthanYoQ/Skill-hubWrote 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/ethanyoq/skill-hub/dsh-pre-push-checks)<a href="https://agentmods.dev/skills/ethanyoq/skill-hub/dsh-pre-push-checks"><img src="https://agentmods.dev/badge/skills/ethanyoq/skill-hub/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/ethanyoq/skill-hub/dsh-pre-push-checks"><img src="https://agentmods.dev/badge/skills/ethanyoq/skill-hub/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.01608 |
| Opus 5.5 | $0.00027 | $0.00643 |
| Sonnet 5.5 | $0.00014 | $0.00322 |
| Haiku 4.5 | $0.00007 | $0.00161 |
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 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.
This is a copy
86% identical to dsh-pre-push-checks — 22 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 — 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
- 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.
- 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:e2etarget when credentials are available; never print secrets.
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 First seen · 116 lines · 68 tokens per session scan A 8d2120972d88
dsh-pre-push-checks is a skill published in the GitHub repository EthanYoQ/Skill-hub (11 stars, last pushed 8d ago), licensed MIT. It adds 68 tokens to every session and 1,608 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to dsh-pre-push-checks, differing in 22 lines, and is treated as a copy.
Other skills, from other repositories
ci-triage
Diagnose failing CI, build, release-gate, or test runs for Cool Workflow. Use when a GitHub Actions check, local npm test, npm run build, release gate, smoke test, or generated-manifest check fails and Codex must identify the first actionable failure with logs and verifier commands.
deploy-check
Verify Cool Workflow release, publish, deploy, or package readiness. Use when Codex must check build/test gates, generated manifests, project index sync, dist/source contract, changelog/release notes, npm package contents, or pre-tag risk before shipping.
design-qa
Evaluate Cool Workflow architecture, product design, operator UX, context-pack, workflow-app, MCP/CLI, or release-process proposals. Use when Codex must decide whether a design respects FreeBSD/POLA, mechanism-not-policy, stable JSON surfaces, evidence, and verifier boundaries before implementation.
pr-description-generator
Generates comprehensive, structured PR descriptions from git diff or branch comparison. Includes summary, changelog, testing notes, and deployment considerations.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
emerging-techniques-model-merging
Merge multiple fine-tuned models using mergekit to combine capabilities without retraining. Use when creating specialized models by blending domain-specific expertise (math + coding + chat), improving performance beyond single models, or experimenting rapidly with model variants. Covers SLERP, TIES-Merging, DARE, Task…