hacs.integration_blueprint: Skill for Claude Code

.agents/skills/ha-release/SKILL.md

ha-release is a skill for Claude Code, Codex from jpawlowski/hacs.integration_blueprint. It costs 217 tokens per session (1,559 once invoked), scanned A, original, MIT.

A set of instructions for releasing a Home Assistant custom integration and preparing its commits. A release is a published version, while commit messages are the short records that determine version changes and changelog entries.

In plain words
What is it for?
It helps decide the next version, write accurate commit messages, prepare release notes, and investigate why an automated release tool missed a change.
Why use it?
It prevents user-visible changes from being hidden under commit types that do not trigger a release or appear in release notes, and requires checking the actual repository changes first.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is jpawlowski/hacs.integration_blueprint's own configuration. It tells Claude Code and Codex how to work on hacs.integration_blueprint itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything hacs.integration_blueprint configures →

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/.agents/skills/ha-release/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/jpawlowski/hacs.integration_blueprint

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.

agentmods badge for ha-release

README.md
[![agentmods](https://agentmods.dev/badge/skills/jpawlowski/hacs.integration_blueprint/ha-release/github.svg)](https://agentmods.dev/skills/jpawlowski/hacs.integration_blueprint/ha-release)
Your own site
<a href="https://agentmods.dev/skills/jpawlowski/hacs.integration_blueprint/ha-release"><img src="https://agentmods.dev/badge/skills/jpawlowski/hacs.integration_blueprint/ha-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.

agentmods 80×15 button for ha-release

Your own site · 80×15
<a href="https://agentmods.dev/skills/jpawlowski/hacs.integration_blueprint/ha-release"><img src="https://agentmods.dev/badge/skills/jpawlowski/hacs.integration_blueprint/ha-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 217 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,559 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00217 $0.01559
Opus 5 $0.00109 $0.00779
Sonnet 5 $0.00043 $0.00312
Haiku 4.5 $0.00022 $0.00156

Measured 12d ago against content hash 699b13ce91fb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

ha-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 12d 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.

.agents/skills/ha-release/SKILL.md · 137 lines

How it starts

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

Releases and commit messages

Releases are driven entirely by commit messages. A sloppy commit subject is not a cosmetic issue here — it decides the version number and what users read in the changelog.

Commit rules for agents (non-negotiable)

  • Never commit automatically. Only commit when the developer explicitly asks, in that message.
  • A previous commit request is not standing permission. Each commit needs a fresh instruction.
  • Never push, and never offer to. The developer handles git push.
  • Always run git diff (and git status) before writing a message. Describe what is actually staged, not what you remember doing.

Commit message format

The format, the allowed types and scopes, the rules commitlint enforces, and the scope-versus-type trap are all in blueprint.commit-message.instructions.md, which Copilot loads for every file. Read it before writing a message.

What that file does not tell you is what your choice costs at release time: a user-facing change committed under a hidden type (refactor, chore, docs, test, ci) never reaches the changelog and never triggers a release — only feat, fix, perf, and breaking changes do. If a change matters to a user, pick one of those honestly instead of reaching for chore.

When you tell someone which type to use, say this consequence out loud — "X, because Y is hidden from the changelog and never ships a release" — don't just name the type and cite the instructions file's definition of it.

What each type does to the release

Type Changelog section Version effect (pre-1.0)
feat Features patch bump (0.1.00.1.1)
fix Bug Fixes patch bump
perf Performance patch bump
feat! / BREAKING CHANGE: Features + notice minor bump (0.1.00.2.0)
refactor, chore, docs, test, ci hidden no release

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

  1. 12d ago First seen · 137 lines · 217 tokens per session scan A 699b13ce91fb

Subscribe to this mod's changes

ha-release is a skill published in the GitHub repository jpawlowski/hacs.integration_blueprint (49 stars, last pushed 5d ago), licensed MIT. It adds 217 tokens to every session and 1,559 once invoked, about $0.0011 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-30.