Borrowing it
Nothing to install: this file belongs to Sivan757/dsh-agent-plugins-market. 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/Sivan757/dsh-agent-plugins-market/main/.agents/skills/market-pre-push-checks/SKILL.mdgit clone --depth 1 https://github.com/Sivan757/dsh-agent-plugins-marketWrote 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/sivan757/dsh-agent-plugins-market/market-pre-push-checks)<a href="https://agentmods.dev/skills/sivan757/dsh-agent-plugins-market/market-pre-push-checks"><img src="https://agentmods.dev/badge/skills/sivan757/dsh-agent-plugins-market/market-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/sivan757/dsh-agent-plugins-market/market-pre-push-checks"><img src="https://agentmods.dev/badge/skills/sivan757/dsh-agent-plugins-market/market-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.00045 | $0.00487 |
| Opus 5.5 | $0.00018 | $0.00195 |
| Sonnet 5.5 | $0.00009 | $0.00097 |
| Haiku 4.5 | $0.00005 | $0.00049 |
Grade A, and why
market-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.
What it actually says
Market Pre-Push Checks
Run evidence matched to the outgoing diff once, then report only the commands run. CI owns exhaustive coverage; the full pnpm run test locally is reserved for release verification (see market-release) and repository-wide changes.
Steps
- Scope the diff.
git status --short --branchandgit diff <base> --stat; the surface list is the completion criterion for this step. - Map surface to evidence and run the union once:
| Outgoing surface | Evidence |
|---|---|
src/** or tests/** |
check:refactor + the vitest files mirroring the touched areas (tests/<area>.test.ts) |
src/client/** or locales.ts |
above + every tests/client-*.test.ts |
schemas/** |
above + packages/market-bundle/test/integration/mcp-config.test.ts + packages/market-catalog/test/lsp-spec.test.ts |
docs/**, README*, docs-site/** |
format:check + pnpm --dir docs-site run check:guide && pnpm --dir docs-site run build && pnpm --dir docs-site run check:links (the build+link pair only when site or guide sources changed) |
package.json / lockfile |
pnpm install --frozen-lockfile + check:refactor + check:host-alignment |
a new import('@deepseek-ai/dsh-*') |
above + check:host-alignment (an undeclared host import is a surface that degrades silently) |
- Re-verify after fixes. Any fix reruns the same command set that failed, nothing more.
- Green tree.
format:checkcovers files eslint does not (docs, HTML, fixtures) — include it whenever non-TS files moved, then report the evidence list with the push proposal.
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.
- 12d ago Changed 2d7141662c72
- 1mo ago Changed · +1 lines 04bddf85622a
- 1mo ago First seen · 25 lines · 45 tokens per session scan A 7e19b1115dde
market-pre-push-checks is a skill published in the GitHub repository Sivan757/dsh-agent-plugins-market (18 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 487 once invoked, about $0.0002 per session on Opus 5.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-05.
Other skills, from other repositories
code-review-zh
A Git-based code review workflow that compares changes from a chosen commit, branch, tag, or merge point. It checks both whether the code follows the repository's written standards and whether it implements the requested specification.
git-workflow
Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes. Use when choosing a branching strategy, writing commit conventions, deciding merge versus rebase, or resolving conflicts.
commit
Use when starting implementation work on a task, or when the user asks you to commit changes to the repository.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
changelog-writing
A writing guide for maintaining a CHANGELOG.md file, which records user-visible changes between software versions. It also covers the release notes taken from the current version section.
nw-quality-framework
Quality gates - 11 commit readiness gates, build/test protocol, validation checkpoints, and quality metrics.