What is release-publish?

A release checklist for senpi, a software project, that guides version tagging, GitHub release creation, and npm package publishing.

Use it to run senpi's CalVer release process, audit changelogs, run checks and tests, create release commits and tags, and publish packages to npm.

It reduces the risk of releasing from the wrong branch, with unverified changes, missing release notes, or failed checks.

How code-yeongyu/senpi configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to code-yeongyu/senpi. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/code-yeongyu/senpi/main/.github/agent/skills/release-publish/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/code-yeongyu/senpi

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/code-yeongyu/senpi/release-publish/github.svg)](https://agentmods.dev/skills/code-yeongyu/senpi/release-publish)

Your own site

<a href="https://agentmods.dev/skills/code-yeongyu/senpi/release-publish"><img src="https://agentmods.dev/badge/skills/code-yeongyu/senpi/release-publish/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/code-yeongyu/senpi/release-publish"><img src="https://agentmods.dev/badge/skills/code-yeongyu/senpi/release-publish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,586 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.

Model	Per session	Once invoked
Fable 5.1	$0.00044	$0.01586
Opus 5.5	$0.00018	$0.00634
Sonnet 5.5	$0.00009	$0.00317
Haiku 4.5	$0.00004	$0.00159

Measured 2mo ago against content hash 1be2850d836b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

release-publish 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 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.

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.

.github/agent/skills/release-publish/SKILL.md · 93 lines

How it starts

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

Release Publish

Use this skill when releasing senpi with the canonical CalVer flow, pushing a release tag, publishing the GitHub Release, or publishing packages to npm.

Canonical release flow

Run scripts/release.mjs from a clean main checkout.

Confirm you are on main.
Confirm the worktree is clean.
Confirm the release version is a valid CalVer.
Run the changelog audit before release.
Make only product-facing release notes from packages/coding-agent/CHANGELOG.md via scripts/release-notes.mjs.
Skip housekeeping, upstream-sync, and generated-catalog-only entries.
Duplicate user-facing ai/agent/tui changes into the coding-agent changelog.
Run npm run check.
Run npm run build.
Run CI=1 npm test.
Create the release commit.
Create the release tag.
Create the next-cycle changelog commit.
Push main and the tag.

Pre-flight checklist

Read the current release rules in AGENTS.md and scripts/AGENTS.md.
Use a clean dedicated clone if the main checkout has foreign state.
Never clean, stash, or otherwise disturb other people's work.
Use the protected-main path when needed; UPSTREAM_AUTOMATION_TOKEN exists for authenticated protected-main pushes.
npm publish is delegated: the tag pipeline's publish-npm job no longer publishes — it dispatches publish-npm.yml in publish-only mode (the proven route from the v2026.7.28-x and v2026.8.4 recoveries) and gates the public GitHub Release on that run's success. npm's trusted publisher matches the publish-npm.yml workflow identity only; never reintroduce a direct publish or an environment: on the publish path (the environment subject is what npm rejects).
Do not rerun scripts/release.mjs after the tag has been pushed.
If checks fail before the tag push, fix first, then re-release from the beginning.
Treat E404 noise for @code-yeongyu/senpi-orchestrator as non-fatal.
Use node scripts/release-notes.mjs / the cl.md audit before publishing notes.
Keep release notes product-facing only.

Read the full file on GitHub · 93 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.

2mo ago First seen · 93 lines · 44 tokens per session scan A 1be2850d836b

Subscribe to this mod's changes

release-publish is a skill published in the GitHub repository code-yeongyu/senpi (511 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 1,586 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-08-30.

Git and workflow LLM Releases agent ai-agent cli coding-agent llm-tools

release-publish next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
release-publishcode-yeongyu/senpi	Skill	511	yesterday	MIT	A	44	Claude Code, Codex
pypi-releasealchemiststudiosDOTai/tunacode	Skill	125	1mo ago	MIT	A	52	Claude Code, Codex
github-repo-managementStarryCod/cogitum	Skill	12	5mo ago	MIT	A	17	Claude Code, Codex
codew-release-qa-sweepHmbown/CodeWhale	Skill	41k	5d ago	MIT	A	31	Claude Code, Codex
gh-credit-harvestHmbown/CodeWhale	Skill	41k	5d ago	MIT	A	30	Claude Code, Codex
releaseHmbown/CodeWhale	Skill	41k	5d ago	MIT	A	0	Claude Code, Codex
githubHmbown/Codewhale	Skill	41k	1mo ago	MIT	A	0	Claude Code, Codex

senpi: Skill for Claude Code