release-checklist

A required set of checks for preparing a software release. It requires a successful migration dry run and a signed changelog before the release is tagged and shipped.

In plain words
What is it for?
Use it as a release gate before tagging and distributing a new version.
Why use it?
It prevents releases from going out without checking database or code migrations and documenting the changes. A dry run tests the migration without applying it permanently.

Skill for Claude CodeCodex

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/tarekkharsa/agentstack/release-checklist
Any agent
npx skills add Tarekkharsa/agentstack --skill release-checklist
Clone the repo
git clone --depth 1 https://github.com/Tarekkharsa/agentstack

Made for: Claude Code, Codex.

Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 48 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.00016 $0.00048
Opus 5 $0.00008 $0.00024
Sonnet 5 $0.00003 $0.00010
Haiku 4.5 $0.00002 $0.00005

Measured 2d ago against content hash f4558f138c41, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

release-checklist 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 2d 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.

examples/projects/skills-workout/bundle/.agentstack/skills/release-checklist/SKILL.md · 7 lines

What it actually says

Release checklist

SENTINEL-REL: no release ships without a green migration dry-run and a signed changelog.

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. 2d ago First seen · 7 lines · 16 tokens per session scan A f4558f138c41

Subscribe to this mod's changes

release-checklist is a skill published in the GitHub repository Tarekkharsa/agentstack (3 stars, last pushed 19d ago), licensed Apache-2.0. It adds 16 tokens to every session and 48 once invoked, about $0.0001 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-31.

Related

Other skills, from other repositories

local-frontend-check

Smoke-test or verify UI behaviour on the local Jarvis Registry frontend running at http://localhost/gateway. Use for manual regression checks, bug-fix verification, and end-to-end confirmation of specific flows without running the automated test suite.

ascending-llc/jarvis-registry · 52 tokens

release-notes

Edit an existing GitHub release's body into the project's bilingual (English + Chinese) template format with a References section built from merged PRs. Use when 修改 release、整理发布说明、release notes、编辑 release 内容、发版后整理、edit release body.

samanhappy/mcphub · 58 tokens

new-feature-design

Design and document new features with GitHub issue, low-level design (LLD), expert review, and testing plan. Creates structured documentation in .scratchpad/ with issue spec, technical design with diagrams and pseudo-code, multi-persona expert review, and a testing plan covering functional (curl and…

agentic-community/mcp-gateway-registry · 118 tokens

release-notes

Create release notes for a new version tag. Gathers all commits, PRs, issues fixed, and breaking changes since a previous release. Creates the release notes markdown file, tags the repo, and pushes. Asks the user to confirm the base version to diff against.

agentic-community/mcp-gateway-registry · 59 tokens

create-milestone

Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.

agentic-community/mcp-gateway-registry · 64 tokens

generate-agent-card

Generate an A2A agent card JSON by analyzing agent source code in a folder or GitHub URL. Studies the code to detect agent name, skills, tools, auth, protocol, and generates a spec-compliant agent card.

agentic-community/mcp-gateway-registry · 50 tokens