A project-specific procedure for preparing a calendar-versioned release, where the version is based on the date. It creates a draft release with a written summary before the generated commit notes.

Creating date-based Git tags, triggering release packaging through CI, adding a release narrative, and opening a draft GitHub release.

It organizes tagging, packaging, release-note preparation, and manual review without publishing the release automatically.

How jongwony/epistemic-protocols configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to jongwony/epistemic-protocols. 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/jongwony/epistemic-protocols/main/.claude/skills/release/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/jongwony/epistemic-protocols

Made for: Claude Code.

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/jongwony/epistemic-protocols/release/github.svg)](https://agentmods.dev/skills/jongwony/epistemic-protocols/release)

Your own site

<a href="https://agentmods.dev/skills/jongwony/epistemic-protocols/release"><img src="https://agentmods.dev/badge/skills/jongwony/epistemic-protocols/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jongwony/epistemic-protocols/release"><img src="https://agentmods.dev/badge/skills/jongwony/epistemic-protocols/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,566 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.00014	$0.02566
Opus 5.5	$0.00006	$0.01026
Sonnet 5.5	$0.00003	$0.00513
Haiku 4.5	$0.00001	$0.00257

Measured 4d ago against content hash 0c3ecbc8c30d, 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 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.

.claude/skills/release/SKILL.md · 161 lines

How it starts

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

Release (project-local)

Creates a CalVer tagged release with a hand-written narrative prepended to the body CI generates via scripts/package.js. Overrides the global /release skill for this repo.

Purpose

Push CalVer tag → CI (release.yml) runs scripts/package.js to build ZIPs + produce dist/release-notes.md, then gh release create --draft --notes-file attaches it
Prepend a hand-written narrative block to the script-generated body so the release surfaces "why this release matters" before the commit list
Leave publish (draft → published) to the user for manual review

Preconditions

Working tree clean, on main (or user-specified branch)
gh authenticated with push access to the target remote (fork or upstream)
Node 22+ on PATH (packaging requires zlib.crc32)

Flow

Phase 1: Tag decision

Previous tag: git describe --tags --abbrev=0 (excludes drafts, gives last tagged commit)
Today: derive YYYY.MM.DD from current date
Candidate tag: v{YYYY.MM.DD}, or v{YYYY.MM.DD}.{N+1} if same-day tag exists
If latest tag is already today's and is Draft (not published), ask whether to re-tag (delete + recreate) or increment .N

Phase 2: Tag push

git tag <tag>
git push origin <tag> → triggers release.yml

Phase 3: Wait for CI draft

Poll gh run list --workflow=release.yml --limit 1 --json status,conclusion,databaseId every 5s, max 12 attempts (60s total)
When status=completed and conclusion=success, fetch draft: gh release view <tag> --json body,url
If still in_progress after 60s: surface run URL and ask user whether to keep waiting
If CI fails: surface logs via gh run view <id> --log-failed, do not proceed to Phase 4. Remediation: fix the cause and retag with .N increment, or clean up the pushed tag with git push origin :refs/tags/<tag> before retrying

Phase 4: Narrative drafting

Analyze commits since previous tag — each line is one merged PR; read a PR's own commits with git log <merge>^1..<merge>^2 when its detail is needed:

git log --oneline --first-parent <prev-tag>..HEAD

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

4d ago Changed 0c3ecbc8c30d
6d ago Changed dc6f94c71bd7
15d ago Changed 8ed222c01dd7
1mo ago First seen · 161 lines · 14 tokens per session scan A 44c1844895ac

Subscribe to this mod's changes

release is a skill published in the GitHub repository jongwony/epistemic-protocols (173 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 2,566 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-08-30.

Claude Code Git and workflow Releases ai-collaboration epistemology metacognition plugin

taiyi-integration

A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.

Dong90/oh-my-taiyiforge · 27 tokens

flow-next-land

Resolve feedback and CI for one named pull request, then merge when authorized and ready. Emits LANDVERDICT. Use when asked to land a pull request.

gmickel/flow-next · 35 tokens

last-tag

Show commits since the last tag in a formatted table. Use when user asks "what changed since last release", "commits since last tag", "last-tag", "what's new", or wants to see recent unreleased changes.

umputun/cc-thingz · 50 tokens

re0-release

Walk a pending change through this repo's shipping and releasing checklist end to end, then tag and publish once confirmed. User-invoked: run it when you've decided to ship.

LilMGenius/paperthin · 40 tokens

plugin-publish

A release guide for publishing Zhin.js plugins to npm, the JavaScript package registry, and to the Zhin plugin marketplace. It covers package metadata, versioning, release checks, and submission requirements.

zhinjs/zhin · 58 tokens

ccb-github

Maintain this CCB project's GitHub-facing release and npm publication surface. Use when preparing, publishing, auditing, or fixing CCB releases; updating README.md, README/zh.md, localized README files, CHANGELOG.md, VERSION, package.json, GitHub release notes/assets, repository description/topics, npm registry state…

SeemSeam/claude_codex_bridge · 76 tokens

epistemic-protocols: Skill for Claude Code