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 agentmods add skills/l3digitalnet/claude-code-plugins/ha-config-migrationnpx skills add L3DigitalNet/Claude-Code-Plugins --skill ha-config-migrationgit clone --depth 1 https://github.com/L3DigitalNet/Claude-Code-PluginsWrote 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/l3digitalnet/claude-code-plugins/ha-config-migration)<a href="https://agentmods.dev/skills/l3digitalnet/claude-code-plugins/ha-config-migration"><img src="https://agentmods.dev/badge/skills/l3digitalnet/claude-code-plugins/ha-config-migration.svg" alt="Measured on agentmods" 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 | $0.00038 | $0.00746 |
| Opus 5 | $0.00019 | $0.00373 |
| Sonnet 5 | $0.00008 | $0.00149 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
ha-config-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 4d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Home Assistant — Config Entry Version Migration
When your config entry schema changes (renaming keys, adding required fields, restructuring data), increment VERSION and implement async_migrate_entry.
Incrementing Versions
# config_flow.py
class MyConfigFlow(ConfigFlow, domain=DOMAIN):
VERSION = 2 # Increment for breaking schema changes
MINOR_VERSION = 1 # Increment for non-breaking additions
async_migrate_entry Template
# __init__.py
async def async_migrate_entry(hass: HomeAssistant, entry: ConfigEntry) -> bool:
"""Migrate old entry to new version."""
_LOGGER.debug("Migrating from version %s.%s", entry.version, entry.minor_version)
# Downgrade guard: a major version newer than this code supports means the user
# rolled HA/the integration back. Fail cleanly — old code cannot read newer-schema
# data, and falling through to `return True` would load it anyway (silent corruption).
if entry.version > 2:
return False
if entry.version == 1:
# Migration from v1 to v2
new_data = {**entry.data}
# Example: rename a key
if "old_key" in new_data:
new_data["new_key"] = new_data.pop("old_key")
# Example: add new required field with default
if "new_field" not in new_data:
new_data["new_field"] = "default_value"
hass.config_entries.async_update_entry(
entry, data=new_data, version=2, minor_version=0
)
# async_update_entry mutates `entry` in place, so this branch sees version=2 within
# the same call — the checks run sequentially (a 1->2->2.1 migration cascades).
if entry.version == 2 and entry.minor_version < 1:
# Minor version migration (non-breaking additions)
new_options = {**entry.options}
new_options.setdefault("new_option", True)
hass.config_entries.async_update_entry(
entry, options=new_options, minor_version=1
)
_LOGGER.info("Migration to version %s.%s successful", entry.version, entry.minor_version)
return True
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.
- 4d ago First seen · 77 lines · 38 tokens per session scan A 05f50dd71551
ha-config-migration is a skill published in the GitHub repository L3DigitalNet/Claude-Code-Plugins (6 stars, last pushed 3d ago), licensed MIT. It adds 38 tokens to every session and 746 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…