A command for preparing a software release according to a separate ha-release procedure. A software release is a published version of a project.

Use it to inspect the next version, run pre-release checks, preview release notes, or update the notes on an existing release-please pull request.

It provides one place to inspect unreleased changes, check the proposed version, preview release notes, and update notes on an existing release pull request. It avoids manually guessing or editing the release version and notes.

How jpawlowski/hacs.integration_blueprint configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to jpawlowski/hacs.integration_blueprint. 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/jpawlowski/hacs.integration_blueprint/main/.claude/commands/release.md

Clone the repo

git clone --depth 1 https://github.com/jpawlowski/hacs.integration_blueprint

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/commands/jpawlowski/hacs.integration_blueprint/release/github.svg)](https://agentmods.dev/commands/jpawlowski/hacs.integration_blueprint/release)

Your own site

<a href="https://agentmods.dev/commands/jpawlowski/hacs.integration_blueprint/release"><img src="https://agentmods.dev/badge/commands/jpawlowski/hacs.integration_blueprint/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/commands/jpawlowski/hacs.integration_blueprint/release"><img src="https://agentmods.dev/badge/commands/jpawlowski/hacs.integration_blueprint/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 196 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.00015	$0.00196
Opus 5.5	$0.00006	$0.00078
Sonnet 5.5	$0.00003	$0.00039
Haiku 4.5	$0.00002	$0.00020

Measured 2mo ago against content hash e187ea7d6782, 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 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.

.claude/commands/release.md · 15 lines

What it actually says

Load the ha-release skill with the Skill tool and follow its procedure exactly — this command does not restate it, so re-read that file rather than relying on what you already know about it, in case it has changed.

With no arguments, inspect the unreleased commits and report the version release-please will derive; do not edit a version or create a release PR manually. check runs the skill's pre-release checklist, notes previews script/release-notes, and apply-notes updates the body of an existing release-please PR after the draft is read.

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 · 15 lines · 15 tokens per session scan A e187ea7d6782

Subscribe to this mod's changes

release is a command published in the GitHub repository jpawlowski/hacs.integration_blueprint (54 stars, last pushed 5d ago), licensed MIT. It adds 15 tokens to every session and 196 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.

Git and workflow Releases hacs hacs-integration home-assistant home-assistant-integration homeassistant-component homeassistant-custom-component

release next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
releasejpawlowski/hacs.integration_blueprint	Command	54	5d ago	MIT	A	15	Claude Code
landgmickel/flow-next	Command	717	yesterday	MIT	A	13	Claude Code
qualityDesko77/claude-code-skills-1c	Command	90	yesterday	MIT	A	18	Claude Code
release-notesOpenHands/extensions	Command	176	yesterday	MIT	A	44	Claude Code
release-managerruvnet/agentic-flow	Command	838	yesterday	none	A	0	Claude Code
release-planalisunstar/OpenSunstar	Command	31	14d ago	Apache-2.0	A	0	Claude Code
doc-changelogchristopherlouet/claude-base	Command	5	6d ago	MIT	A	0	Claude Code

hacs.integration_blueprint: Command for Claude Code