release

release is a skill for Claude Code, Codex from runxhq/runx. It costs 23 tokens per session (1,141 once invoked), scanned A, original, Apache-2.0.

A governed workflow for releasing a versioned package or project using commands already defined by that project. It prepares, approves, publishes, and independently checks the release while recording evidence.

In plain words
What is it for?
Use it to run a project's preparation, publishing, and verification commands under an approved release profile.
Why use it?
It adds a consistent approval and verification trail without guessing how a particular project builds or publishes. This reduces the risk of running the wrong release commands or treating an incomplete publication as successful.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to run a project's preparation, publishing, and verification commands under an approved release profile.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/runxhq/runx/release
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 runxhq/runx --skill release
Clone the repo
git clone --depth 1 https://github.com/runxhq/runx

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.

agentmods badge for release

README.md
[![agentmods](https://agentmods.dev/badge/skills/runxhq/runx/release/github.svg)](https://agentmods.dev/skills/runxhq/runx/release)
Your own site
<a href="https://agentmods.dev/skills/runxhq/runx/release"><img src="https://agentmods.dev/badge/skills/runxhq/runx/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.

agentmods 80×15 button for release

Your own site · 80×15
<a href="https://agentmods.dev/skills/runxhq/runx/release"><img src="https://agentmods.dev/badge/skills/runxhq/runx/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,141 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.01141
Opus 5.5 $0.00009 $0.00456
Sonnet 5.5 $0.00005 $0.00228
Haiku 4.5 $0.00002 $0.00114

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

Security

Grade A, and why

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.

The scan reads SKILL.md. This mod also ships 2 executable files (fixtures/support/setup_release_fixture.mjs, release.mjs), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/release/SKILL.md · 113 lines

How it starts

The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release

A release is a project-owned operation, not a universal shell recipe. This skill gives Runx one common governance sequence—prepare, describe, approve, publish, and independently verify—while leaving the actual build and provider commands in a versioned profile owned by the project.

Use it when a package or project already knows how to prepare, publish, and verify itself but needs one digest-bound approval and receipt chain around those commands. Do not use it to invent a release process for an unconfigured project or to replace the project's tests, packaging, or registry tooling.

A release profile is the project adapter. It declares exact argv commands that the project already owns; this skill validates their release semantics but does not recreate the project's release implementation.

Runx core owns bounded profile reads, path and symlink containment, command-plan digests, sanitized child environments, process-tree supervision, timeouts, credential redaction, and output evidence. Package JavaScript only validates the release profile and interprets the three release-specific provider states.

Use prepare to execute the profile's preparation command and produce an evidence-bound release brief. Use the default release runner to approve the exact publish plan, execute it without a shell, then run a separate verification command. The publish command is refused if its normalized argv plan drifts after approval. Publication is never inferred from an agent answer or a zero exit code.

Project profile

project_root is resolved inside the current Runx workspace and must be a relative directory (normally . when Runx is invoked from the project root). profile_path must name a JSON file inside that directory:

{
  "schema": "runx/release.profile.v1",
  "id": "my-project/npm",
  "channel": "npm",
  "commands": {
    "prepare": { "argv": ["pnpm", "release:check"], "cwd": ".", "timeout_ms": 300000 },
    "publish": { "argv": ["gh", "workflow", "run", "release.yml"], "cwd": "." },
    "verify": { "argv": ["pnpm", "release:check:live"], "cwd": "." }
  }
}

Read the full file on GitHub · 113 lines

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.

  1. 5d ago Changed 088103a00516
  2. 18d ago Changed · -2 lines 1fa7978a5f4f
  3. 1mo ago First seen · 115 lines · 23 tokens per session scan A 2d08998848cf

Subscribe to this mod's changes

release is a skill published in the GitHub repository runxhq/runx (105 stars, last pushed today), licensed Apache-2.0. It adds 23 tokens to every session and 1,141 once invoked, about $0.0001 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-03.