What is market-release?

A release workflow for publishing a new version of a software package. It uses release-please to create a release pull request, then creates a tag, a GitHub release, and an npm publication after the pull request is merged.

Use it to check the project, determine the version change from commit history, prepare a release, and verify the automated publication flow.

It provides an ordered release process and prevents remote changes such as pushing or publishing without explicit user confirmation.

market-release — Skill for Claude Code and Codex by Sivan757

Install

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.

Any agent

npx skills add Sivan757/dsh-agent-plugins-market --skill market-release

Clone the repo

git clone --depth 1 https://github.com/Sivan757/dsh-agent-plugins-market

Made for: Claude Code, 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/sivan757/dsh-agent-plugins-market/market-release/github.svg)](https://agentmods.dev/skills/sivan757/dsh-agent-plugins-market/market-release)

Your own site

<a href="https://agentmods.dev/skills/sivan757/dsh-agent-plugins-market/market-release"><img src="https://agentmods.dev/badge/skills/sivan757/dsh-agent-plugins-market/market-release/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/sivan757/dsh-agent-plugins-market/market-release"><img src="https://agentmods.dev/badge/skills/sivan757/dsh-agent-plugins-market/market-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 560 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 original No closer match found 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.

Model	Per session	Once invoked
Fable 5.1	$0.00067	$0.00560
Opus 5	$0.00034	$0.00280
Sonnet 5	$0.00013	$0.00112
Haiku 4.5	$0.00007	$0.00056

Measured 5d ago against content hash 5a63fdd9792a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

market-release 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 5d 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.

.agents/skills/market-release/SKILL.md · 22 lines

What it actually says

Market Release

Releases are workflow-owned: release-please (embedded in .github/workflows/npm-publish.yml) opens the Release PR against main, and merging it auto-tags, auto-creates the GitHub Release, and auto-publishes npm. The full runbook lives at docs/release/release-process.md; read it before acting.

Hard rule

Every remote write — git push, git tag, npm publish — requires explicit user confirmation before execution. An agent-initiated push or publish without confirmation is a defect, even when every check is green.

Steps

Verify the outgoing tree. Run check:refactor and pnpm run test; both green is the completion criterion. Fix drift before any release talk (see market-pre-push-checks for the surface-to-check mapping).
Classify the version. Read git log since the latest dsh-agent-plugins-market-v* tag: any feat: → minor, only fix:/perf: → patch, feat!/BREAKING CHANGE: → major. State the expected next version to the user before pushing.
Propose the push and wait for confirmation. After the user confirms, push main; docs/**, README*, and CI-only paths are in paths-ignore and do not trigger release-please.
Verify the Release PR. gh pr list for the chore(main): release PR; check package.json version, CHANGELOG section, and .release-please-manifest.json agree with the classified version, and quality/CodeQL runs are green.
Propose the merge and wait for confirmation. Merging is the one mandatory manual step; after it, watch the npm-publish run on the merge commit — tag, GitHub Release, and npm publish are automatic.
Report and close out. Confirm tag + Release + npm view @deepseek-ai/dsh-agent-plugins-market dist-tags, then offer the post-release items from docs/release/release-v<version>.md (Highlights on the auto-generated Release body, announcements).

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.

5d ago First seen · 22 lines · 67 tokens per session scan A 5a63fdd9792a

Subscribe to this mod's changes

market-release is a skill published in the GitHub repository Sivan757/dsh-agent-plugins-market (8 stars, last pushed today), licensed MIT. It adds 67 tokens to every session and 560 once invoked, about $0.0003 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-09-05.

Git and workflow Releases agent-plugins agentic-ai deepseek-harness dsh dsh-plugin mcp

release-deploy

A release and deployment skill for preparing a software project for GitHub publication and putting it online.

songoao25/dsh-virtual-product-team · 59 tokens

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.

gongyijie85/dsh-ecc · 54 tokens

github-ops

GitHub repository operations, automation, and management. Issue triage, PR management, CI/CD operations, release management, and security monitoring using the gh CLI. Use when the user wants to manage GitHub issues, PRs, CI status, releases, contributors, stale items, or any GitHub operational task beyond simple git…

gongyijie85/dsh-ecc · 71 tokens

opensource-pipeline

Open-source pipeline: fork, sanitize, and package private projects for safe public release. Chains 3 agents (forker, sanitizer, packager). Triggers: '/opensource', 'open source this', 'make this public', 'prepare for open source'. Use when a private project must be forked, stripped of secrets, and packaged for public…

gongyijie85/dsh-ecc · 76 tokens

release

Step through versioning, tagging, and verification.

Devin-AXIS/iPolloWork · 11 tokens

dsh-changelog

A release-note writing guide for maintaining a CHANGELOG, a file that records what changed in each software version. It follows Keep a Changelog categories and semantic versioning rules.

hackerFish/awesome-dsh-skills · 30 tokens