A release checklist for publishing updates to the claude-code-harness plugin repository. It covers deciding whether a Git tag is needed, updating plugin versions, recording the change, staging files, publishing, and checking that the remote repository is synchronized.

Use it when releasing changes to the harness plugin or its shipped files. It helps decide the release path and verify the final commit, tag, push, and version state.

It reduces release mistakes such as mismatched versions, missing tags, or changes documented but never pushed. Version updates ensure installed users can receive changed plugin files.

release — Skill for Claude Code by nikitaCodeSave/claude-code-harness

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/nikitaCodeSave/claude-code-harness

agentmods

npx agentmods add skills/nikitacodesave/claude-code-harness/release

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/nikitacodesave/claude-code-harness/release/github.svg)](https://agentmods.dev/skills/nikitacodesave/claude-code-harness/release)

Your own site

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

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

When invoked 3,002 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.

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.00076	$0.03002
Opus 5.5	$0.00030	$0.01201
Sonnet 5.5	$0.00015	$0.00600
Haiku 4.5	$0.00008	$0.00300

Measured 1mo ago against content hash f04eb08b7e10, 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 1mo 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 · 189 lines

How it starts

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

Релиз / обновление репозитория claude-code-harness

Этот репозиторий — source of truth публичного плагина. Консюмеры устанавливают из origin/main через /plugin update. Отсюда два жёстких факта, которые формируют весь ритуал:

Версия в plugin.json — это update cache key. Правка shipped-поверхности БЕЗ бампа версии доставляет подписчикам ничего (см. native-capabilities.md §Plugins). Значит любое изменение под plugins/** обязано пройти через релиз с бампом.
Релиз существует только когда запушен (коммит + тег + push в origin). Незапушенный релиз — это анонс в devlog без поставки. Три прошлых релиза сломались именно тут (desync версий, стампы на несуществующих версиях, «зарелизил в devlog, но не запушил») — ради этого и написан scripts/release.sh.

Не переизобретай механику: plugins/harness/scripts/release.sh уже бампит обе версии, стережёт drift и стейджит поверхность. Этот скилл — рунбук поверх него: решение + пред-шаги + финиш + верификация, то, что скрипт намеренно не делает.

Шаг 0. Развилка — нужен ли тег?

Посмотри git status / git diff --stat. Задевает ли изменение shipped-поверхность?

Shipped-поверхность = plugins/** · README.md · CHANGELOG.md · .claude-plugin/marketplace.json. → Путь B (Релиз): version bump + тег.
Только dev-harness = .claude/** (CLAUDE.md, этот скилл, devlog-правка) · .gitignore · .gitattributes · LICENSE. → Путь A (Dev-harness commit): обычный commit + push, без бампа, без тега.

Пограничный случай: изменение задевает и то, и другое (например, правка reference + правка CLAUDE.md). Тогда это Путь B — раз shipped-поверхность затронута, нужен релиз; dev-harness-файлы просто едут в том же коммите.

Ты работаешь в main (консюмеры ставят из origin/main) — релизы идут прямо в main, это установившийся поток. Убедись, что ты на main и что пользователь действительно просил опубликовать, прежде чем пушить.

Путь A — dev-harness фикс (без тега)

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

1mo ago First seen · 189 lines · 76 tokens per session scan A f04eb08b7e10

Subscribe to this mod's changes

release is a skill published in the GitHub repository nikitaCodeSave/claude-code-harness (4 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 3,002 once invoked, about $0.0003 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-31.

Git and workflow Releases

release-announcement

Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.

paperclipai/paperclip · 42 tokens

release-notes

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

phuryn/pm-skills · 57 tokens

release