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.
npx skills add nolte/claude-home-assistant --skill ha-hacs-releasegit clone --depth 1 https://github.com/nolte/claude-home-assistantWrote 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.
[](https://agentmods.dev/skills/nolte/claude-home-assistant/ha-hacs-release)<a href="https://agentmods.dev/skills/nolte/claude-home-assistant/ha-hacs-release"><img src="https://agentmods.dev/badge/skills/nolte/claude-home-assistant/ha-hacs-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.
<a href="https://agentmods.dev/skills/nolte/claude-home-assistant/ha-hacs-release"><img src="https://agentmods.dev/badge/skills/nolte/claude-home-assistant/ha-hacs-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00208 | $0.01878 |
| Opus 5 | $0.00104 | $0.00939 |
| Sonnet 5 | $0.00042 | $0.00376 |
| Haiku 4.5 | $0.00021 | $0.00188 |
Grade A, and why
ha-hacs-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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HA HACS Release
Spec: spec/claude/ha-hacs-release/en.md (EN canonical) / spec/claude/ha-hacs-release/de.md (DE translation).
This skill operationalizes spec/ha/hacs-release/en.md — the HACS-specific distribution layer (hacs.json, version alignment, ZIP release, brands) — on top of the portfolio's generic release-automation flow. It closes the audit finding that the ha/hacs-release spec exists but no skill or agent makes a consumer integration HACS-release-ready.
Why this is a skill, not an agent
- Human-visible augmentation surface — the user reads back
hacs.json, the version-alignment check, and the ZIP-CD wiring and confirms the distribution model; a skill keeps this on the visible command surface. - Mid-flow interactivity — the ZIP-vs-default-branch distribution choice, the minimum HA version, and whether
brandsis already registered are per-run dialogues the user confirms. - Orchestrator-leaning — it surfaces the generic
release-automationprerequisites and points atnolte/gh-plumbingreusable workflows rather than duplicating release logic; the skill-orchestrates default keeps it in skill form. - Counter-dimension considered: the verify loop could be an agent, but the distribution-model decision and the report belong in the user's working context; skill wins.
When this skill activates
Use this skill to make an existing integration installable and updatable through HACS — scaffold or verify hacs.json, the manifest/tag version alignment, and the ZIP-release CD obligation — per ha/hacs-release.
When NOT to activate
- the generic release publish flow (Draft → Published,
chore(release)alignment, version-bearing files) →spec/project/release-automation(operationalized bynolte-shared:release-publish-trigger) - the CI validation workflow (hassfest / HACS action / pytest) →
ha-integration-ci-scaffold - generating the Python integration code →
ha-integration-scaffold - deploying/importing into a running HA instance → out of scope
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.
- 12d ago First seen · 94 lines · 208 tokens per session scan A 574124cdb7f0
ha-hacs-release is a skill published in the GitHub repository nolte/claude-home-assistant (1 stars, last pushed 1mo ago), licensed MIT. It adds 208 tokens to every session and 1,878 once invoked, about $0.0010 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.
Other skills, from other repositories
security-compliance
Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and risk assessments, managing security operations and incident response, and embedding security throughout the SDLC.
stride-analysis-patterns
Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.
review-loop
Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…
prompts-chat
Use when searching, installing, or improving AI skills and prompts via prompts.chat or skills.sh. Triggers on skill search, prompt lookup, install skill, improve prompt, prompts.chat.
writing-fragments
Grilling session that mines the user for fragments — heterogeneous nuggets of writing (claims, vignettes, sharp sentences, half-thoughts) — and appends them to a single document as raw material for a future article. Use when the user wants to develop ideas before imposing structure, or mentions "fragments", "ideate"…
caveman-help
Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".