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-backup-platform-addgit 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-backup-platform-add)<a href="https://agentmods.dev/skills/nolte/claude-home-assistant/ha-backup-platform-add"><img src="https://agentmods.dev/badge/skills/nolte/claude-home-assistant/ha-backup-platform-add/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-backup-platform-add"><img src="https://agentmods.dev/badge/skills/nolte/claude-home-assistant/ha-backup-platform-add.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.00194 | $0.01844 |
| Opus 5 | $0.00097 | $0.00922 |
| Sonnet 5 | $0.00039 | $0.00369 |
| Haiku 4.5 | $0.00019 | $0.00184 |
Grade A, and why
ha-backup-platform-add 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 10d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HA Backup Platform Add
Spec: spec/claude/ha-backup-platform-add/en.md (EN canonical) / spec/claude/ha-backup-platform-add/de.md (DE translation).
Why this is a skill, not an agent
- Human-visible augmentation surface — the user describes the integration type and reads back the
backup.pymodule and the conformance report; a skill keeps this on the visible command surface, like the sibling augment skills (ha-config-flow-augment,ha-coordinator-add,ha-repairs-add,ha-device-automation-add). - Mid-flow interactivity — the hooks-vs-agent disambiguation is a per-run dialogue the user approves before generation.
- Bounded, inline generation — one platform module (the two hook functions, or the agent class plus its registration) fits inline; no isolated agent context is needed.
- Counter-dimension considered: the draft→validate loop could be an agent, but the surface decision belongs in the user's working context; skill wins.
When this skill activates
Use this skill to add one backup-platform surface — pre/post backup hooks (for DB-writing or stateful integrations) or a backup agent (for storage-providing integrations) — to an existing integration via its backup.py platform module.
When NOT to activate
- greenfield integration scaffolding →
ha-integration-scaffold - the sibling diagnostics platform module →
ha-diagnostics-augment - backup encryption, retention, scheduling, or restore orchestration → owned by the backup manager / HA core, out of scope
- deploying/importing into a running HA instance → out of scope
Hard rules
- One surface, one run. Either pre/post hooks or a backup agent — no combined batch.
- Read
spec/ha/backup-platform/en.mdfirst. Do not generate from memory. - Disambiguate the surface. Stateful / DB-writing integration → pre/post hooks; storage-providing (cloud-storage) integration → backup agent. When both apply, have the user pick the one this run augments.
- Hooks contract.
async_pre_backup(hass: HomeAssistant) -> Noneandasync_post_backup(hass: HomeAssistant) -> Noneare top-level async functions; whateverasync_pre_backuppauses,async_post_backupresumes. - Agent registration.
async_get_backup_agents(hass)returnslist[BackupAgent]and must return[]when no loaded config entry exists for the domain (hass.config_entries.async_loaded_entries(DOMAIN)).async_register_backup_agents_listener(hass, *, listener, **kwargs)is a@callbackreturning an unregister function; notify listeners duringasync_setup_entry. - Agent contract. The
BackupAgentsubclass (fromhomeassistant.components.backup) setsdomain/name/unique_idand implementsasync_upload_backup,async_download_backup,async_list_backups,async_get_backup, andasync_delete_backup— the full abstract interface. - Error semantics. Errors raise
BackupAgentError(or a subclass) — no other exception leaves the agent; a missing backup raisesBackupNotFoundinasync_download_backup/async_delete_backup/async_get_backup. Call theon_progresscallback periodically inasync_upload_backup. - No backup-manager territory. Never implement encryption, retention, scheduling, or restore orchestration; those belong to the backup manager or the core.
- Name per
spec/ha/naming-conventions/en.mdand verify HA internals against the official docs (seespec/ha/upstream-docs-verification/en.md).
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.
- 10d ago First seen · 105 lines · 194 tokens per session scan A 2113e0cd380f
ha-backup-platform-add is a skill published in the GitHub repository nolte/claude-home-assistant (1 stars, last pushed 1mo ago), licensed MIT. It adds 194 tokens to every session and 1,844 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
embedded-iot
Embedded systems firmware, microcontrollers (ESP32, STM32, Arduino, Raspberry Pi), RTOS (FreeRTOS, Zephyr), IoT protocols (MQTT, CoAP, BLE), bare-metal C/C++, and hardware peripheral interfaces (I2C, SPI, UART, GPIO). Use when developing firmware, working with microcontrollers, or building IoT devices.
spark-environment-setup
Set up a working ML training/inference environment on NVIDIA DGX Spark (GB10, aarch64, CUDA 13). Use when installing PyTorch/Unsloth/TRL/vLLM on DGX Spark, hitting libcudart or wheel-ABI errors on aarch64, or choosing between NGC containers and bare pip installs.
spark-training-gotchas
Preflight and diagnose the ten known failure modes for ML training on NVIDIA DGX Spark. Use when a training run on DGX Spark fails to start, OOMs below the 128GB limit, slows down mid-run, or before any multi-hour training job on GB10.
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"…