What is ha-migration?

A guide for updating Home Assistant integrations when stored configuration changes or older programming interfaces are removed. Home Assistant is software for controlling and connecting smart-home devices.

Use it when changing saved configuration data, upgrading the minimum Home Assistant version, seeing deprecation warnings, or checking an integration for common migration problems.

It helps preserve existing users’ settings during schema changes and addresses warnings or failures caused by deprecated Home Assistant APIs.

ha-migration — Skill for Claude Code by L3DigitalNet

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add L3DigitalNet/Claude-Code-Plugins

Claude Code

/plugin install home-assistant-dev

Made for: Claude Code.

Or install home-assistant-dev, the plugin that ships this one along with the rest of its 27 skills, 2 commands, 3 agents, 1 hook.

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/l3digitalnet/claude-code-plugins/ha-migration/github.svg)](https://agentmods.dev/skills/l3digitalnet/claude-code-plugins/ha-migration)

Your own site

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

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

When invoked 370 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.00034	$0.00370
Opus 5.5	$0.00014	$0.00148
Sonnet 5.5	$0.00007	$0.00074
Haiku 4.5	$0.00003	$0.00037

Measured 1mo ago against content hash 1f2200c8b015, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ha-migration 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.

plugins/home-assistant-dev/skills/ha-migration/SKILL.md · 44 lines

What it actually says

Home Assistant Integration Migration

This skill is an entry point for two distinct migration concerns:

Config Entry Version Migration

When your config entry schema changes (renaming keys, adding required fields), you need to increment VERSION and implement async_migrate_entry.

See ha-config-migration for the full pattern and template.

When to use it: You changed what's stored in entry.data or entry.options and existing users' data needs to be transformed.

Deprecation Fixes

When upgrading to a newer HA version, imports, type annotations, and API patterns that were deprecated may now emit warnings or fail.

See ha-deprecation-fixes for 2024–2025 deprecation patterns with before/after examples.

When to use it: You see deprecation warnings in HA logs, or you're upgrading homeassistant minimum version in hacs.json.

Migration Checklist (Per Version Upgrade)

Check the Home Assistant Developer Blog for breaking changes
Search for deprecated imports in your code

Run check-patterns.py to detect common issues:

python3 "${CLAUDE_PLUGIN_ROOT}/scripts/check-patterns.py" custom_components/my_integration/

Update minimum HA version in hacs.json
Test against target HA version

Config entry migration → ha-config-migration
Deprecation patterns → ha-deprecation-fixes
Integration structure → ha-integration-scaffold

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 · 44 lines · 34 tokens per session scan A 1f2200c8b015

Subscribe to this mod's changes

ha-migration is a skill published in the GitHub repository L3DigitalNet/Claude-Code-Plugins (8 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 370 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-31.

Hardware and IoT

gke-compute-classes

Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…

google/skills · 83 tokens

jetson-diagnostic

Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.

NVIDIA/skills · 30 tokens

offensive-z-wave

Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…

SnailSploit/Claude-Red · 113 tokens

doca-socket-relay

Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…

NVIDIA/skills · 236 tokens

hsb-flash

Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…

NVIDIA/skills · 94 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens