agentmods.dev

release

release is a skill for Claude Code, Codex from nexus-substrate/nexus-agents. It costs 39 tokens per session (1,540 once invoked), scanned A, original, MIT.

A release checklist and workflow for publishing a new software version, creating release tags, or deploying a project. It covers tests, security checks, documentation, and migration notes.

In plain words
What is it for?
Running project checks before a release, reviewing vulnerabilities and secrets, confirming changelog entries, and following the project’s release standards.
Why use it?
It helps verify that a version is ready and that important quality, security, and documentation tasks are not skipped.

Skill for Claude CodeCodex

Part of the nexus-agents plugin — 33 skills, 16 agents, 1 hook shipped together

not rated 18 today A scan 39 tokens original MIT
View the source file nexus-substrate/nexus-agents
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.

agentmods
npx agentmods add skills/nexus-substrate/nexus-agents/release
Any agent
npx skills add nexus-substrate/nexus-agents --skill release
Clone the repo
git clone --depth 1 https://github.com/nexus-substrate/nexus-agents

Made for: Claude Code, Codex.

Or install nexus-agents, the plugin that ships this one along with the rest of its 33 skills, 16 agents, 1 hook.

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/nexus-substrate/nexus-agents/release.svg)](https://agentmods.dev/skills/nexus-substrate/nexus-agents/release)
Your own site
<a href="https://agentmods.dev/skills/nexus-substrate/nexus-agents/release"><img src="https://agentmods.dev/badge/skills/nexus-substrate/nexus-agents/release.svg" alt="Measured on agentmods" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,540 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00039 $0.01540
Opus 5 $0.00019 $0.00770
Sonnet 5 $0.00008 $0.00308
Haiku 4.5 $0.00004 $0.00154

Measured 4d ago against content hash 6ac6445382c1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 4d 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.

skills/release/SKILL.md · 139 lines

How it starts

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

Release Skill

Pre-launch checklist (run before tagging)

The pnpm changeset workflow handles versioning, but the human-judgment gates below decide whether the release is ready. Run all of these:

Code quality

  • pnpm lint && pnpm typecheck && pnpm test — green
  • pnpm coverage — coverage hasn't regressed below the gate (89.66% statements, 93.26% functions per CLAUDE.md)
  • No TODO / FIXME / XXX comments in production source added in this release that should have been resolved
  • No console.log debugging statements in production code
  • All @deprecated markers added in this release have a clear replacement and migration path (see deprecation-and-migration skill)

Security

  • pnpm audit shows no critical/high vulnerabilities (or each is documented + mitigated)
  • No new secrets, env vars, or credentials added without .env.example placeholder + docs
  • CodeQL alerts at 0 high/critical (see security-scanning skill)
  • gh api repos/{owner}/{repo}/dependabot/alerts?state=open returns clean

Documentation

  • CHANGELOG entry exists for every public-API change (changesets handles this if pnpm changeset was run)
  • Migration recipe in changeset for any breaking change (typed-only or runtime)
  • inject-governance.ts regen ran cleanly (CLAUDE.md skill table, AGENTS.md, marketplace.json all in sync)
  • No stale @deprecated references in docs/

Pipeline health

  • Last 5 release runs on main succeeded (gh run list --workflow=Release --limit 5)
  • No release PR currently open (gh pr list --search "version packages") — if one IS open, merge it FIRST (a stale version PR is how npm gets ahead of main); see "Avoid the publish race" below
  • npm view nexus-agents version matches packages/nexus-agents/package.json — the Detect npm-ahead version skew step in release.yml also enforces this, but check before tagging
  • No changeset debt — every recent shippable-source PR shipped its own changeset (the Changeset Presence CI gate enforces this going forward)

Read the full file on GitHub · 139 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. 4d ago First seen · 139 lines · 39 tokens per session scan A 6ac6445382c1

Subscribe to this mod's changes

release is a skill published in the GitHub repository nexus-substrate/nexus-agents (18 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 1,540 once invoked, about $0.0002 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-08-30.

CI and CDDevOps and cloudGit and workflowReleases
Related

Other skills, from other repositories

ship

Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. (gstack).

garrytan/gstack · 35 tokens

agent-github-modes

Agent skill for github-modes - invoke with $agent-github-modes.

ruvnet/ruflo · 21 tokens

tutti-app-release

Set up, review, run, or debug external repositories that publish a Tutti workspace app through the reusable Tutti App Release GitHub Actions workflow. Use for caller workflows, tutti.app.json manifests, @tutti-os/app-release-tools, S3/CloudFront release hosting, latest.json, versions.json, catalog.json, catalog-only…

tutti-os/tutti · 80 tokens

harness-release

Generic release automation for projects using Keep a Changelog + GitHub. Single confirmation gate then end-to-end automation: bump detection, CHANGELOG promotion, PR/main merge, tag, GitHub Release. Trigger: release, version bump, publish. Do NOT load for: implementation, review, planning, setup.

Chachamaru127/claude-code-harness · 66 tokens

publish

Publish the Octop Python package: cut a release branch from develop, bump version, update CHANGELOG, open a PR to main; after merge, Actions tag on main (PyPI / Docker Hub + GHCR) and sync main into develop. Use when the user asks to publish, release, bump version, cut a release, or run /publish.

TencentCloud/Octop · 74 tokens

releasepr

Guides adoption and use of pr-release in a consuming repository: installation, GitHub Actions wiring, configuration, conventional-commit release PRs, explicit beta/stable/legacy plans, custom notes, dry-runs, publication lifecycle, and troubleshooting. Use when a project depends on compozy/releasepr. Not for editing…

compozy/compozy · 78 tokens