Borrowing it
Nothing to install: this file belongs to dashpay/platform. 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/dashpay/platform/v5.1-dev/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/dashpay/platformWrote 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/dashpay/platform/release)<a href="https://agentmods.dev/skills/dashpay/platform/release"><img src="https://agentmods.dev/badge/skills/dashpay/platform/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.
<a href="https://agentmods.dev/skills/dashpay/platform/release"><img src="https://agentmods.dev/badge/skills/dashpay/platform/release.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.00061 | $0.04157 |
| Opus 5.5 | $0.00024 | $0.01663 |
| Sonnet 5.5 | $0.00012 | $0.00831 |
| Haiku 4.5 | $0.00006 | $0.00416 |
Grade C, and why
release scanned grade C with 2 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 2mo 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -s https://registry.npmjs.org/@dashevo/<pkg>/<version> | python3 -c "import sys,json;print(json.load(sys.stdin).get('_npmUser'))" Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s https://registry.npmjs.org/@dashevo/<pkg>/<version> | python3 -c "import sys,json;print(json.load(sys.stdin).get('_npmUser'))" How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cut a Platform release
yarn release (→ scripts/release/release.sh) bumps every workspace version, regenerates the changelog, and opens a release PR. It does not publish artifacts or tag — a maintainer merges the PR, then publishes a GitHub release, which creates the tag and triggers the asset build (see Publishing the GitHub release below).
Full flow: yarn release → fix offset versions on the PR → merge → publish the GitHub release (tags + builds assets).
What one run does
- Bumps the version in all npm
package.jsonfiles, the rootpackage.json, and the[workspace.package]version inCargo.toml(all Rust crates inherit it). - Runs
cargo metadatato refreshCargo.lock. - Regenerates
CHANGELOG.md(conventional-changelog,dashpreset) from the changelog-base tag to HEAD. - Creates branch
release_<new-version>, commitschore(release): update changelog and version to <new-version>. - Pushes the branch and opens a PR against the branch you ran it from (e.g.
v4.1-dev), body fromscripts/release/pr_description.md, assigned to a milestone.
Command
yarn release -v=<target-version> # explicit exact version — preferred, unambiguous
yarn release -t=<type> # derive next version from current + type
yarn release -c=<tag> # override the changelog-from tag (optional)
-v/--version— set the exact version (validated as semver). The type is inferred from the prerelease id. Prefer this — no guessing.-t/--type—release, or a prerelease id:dev,alpha,beta,rc(any id works). Version is derived from the current version (see rules below).-c/--changelog-from— tag to build the changelog from. Omit to auto-detect viafind_latest_tag.js.
-t derivation rules (from bump_version.js, when -v is not given)
Given current root version and its type:
- release → same type
release: patch bump (4.0.0→4.0.1). - release → a prerelease type: minor bump +
.1(4.0.0-t=beta→4.1.0-beta.1). - prerelease →
release: minor bump, drop prerelease (4.1.0-beta.3-t=release→4.1.0). - prerelease → different prerelease type: retarget
X.Y.0-<newtype>.1(4.1.0-dev.5-t=beta→4.1.0-beta.1). - prerelease → same prerelease type: prerelease bump (
4.1.0-beta.1-t=beta→4.1.0-beta.2).
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.
- 2mo ago First seen · 167 lines · 61 tokens per session scan C 3a77600450df
release is a skill published in the GitHub repository dashpay/platform (93 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 4,157 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
pump-build-release
Build and release pipeline for the Pump SDK — tsup TypeScript builds, Cargo release profiles, semantic release with commitizen, npm publishing, linting, Makefile targets, Vercel deployment, and MCP server distribution.
github-repo-management
Clone/create/fork repos; manage remotes, releases.
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
doc-changelog-writer
Generate CHANGELOG.md entries from git commits.
github-pr-workflow
GitHub PR lifecycle: branch, commit, open, CI, merge.