What is ha-delete-config?

A removal tool for Home Assistant automations and scripts. Automations are rules that make devices act when specified conditions occur; scripts are reusable sequences of actions.

Use it to find and delete a specific automation or script through Home Assistant’s REST interface.

It helps remove unwanted configurations while requiring the operator to confirm the exact target first. It also explains when a configuration must instead be deleted from YAML files.

ha-delete-config — Skill for Claude Code by gtapps

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 gtapps/claude-code-hermit

Claude Code

/plugin install claude-code-homeassistant-hermit

Made for: Claude Code.

Or install claude-code-homeassistant-hermit, the plugin that ships this one along with the rest of its 18 skills, 3 agents.

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/gtapps/claude-code-hermit/ha-delete-config.svg)](https://agentmods.dev/skills/gtapps/claude-code-hermit/ha-delete-config)

Your own site

<a href="https://agentmods.dev/skills/gtapps/claude-code-hermit/ha-delete-config"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/ha-delete-config.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 579 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.00037	$0.00579
Opus 5	$0.00018	$0.00290
Sonnet 5	$0.00007	$0.00116
Haiku 4.5	$0.00004	$0.00058

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

Security

Grade A, and why

ha-delete-config 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.

plugins/claude-code-homeassistant-hermit/skills/ha-delete-config/SKILL.md · 40 lines

How it starts

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

Delete HA Config

Removes an automation or script from Home Assistant via DELETE /api/config/{domain}/config/{id}.

Steps

Identify the target: Ask the operator which automation or script to delete (name or ID).
- If unknown, list options: ${CLAUDE_PLUGIN_ROOT}/bin/ha-agent-lab ha list-automations or ha list-scripts.
- The id column is the config ID needed for deletion. The friendly_name column shows the UI display name (this is HA's friendly_name attribute, which may differ from the YAML alias: field if the operator customized it via the UI).
- The deletable column is false for YAML-packaged automations (no numeric id) — these cannot be removed via REST. Tell the operator to delete the YAML block from their config files and reload manually instead.
Confirm with operator: Show the target details (entity_id, id, friendly_name, state) and ask for explicit confirmation before proceeding. This action cannot be undone via CLI.
Delete: Run the appropriate command:
- ${CLAUDE_PLUGIN_ROOT}/bin/ha-agent-lab ha delete-automation <id> for automations.
- ${CLAUDE_PLUGIN_ROOT}/bin/ha-agent-lab ha delete-script <id> for scripts.
Check result: Read the JSON output.
- ok: true — config deleted. The entity stays in the registry until the next reload.
- ok: false, message: "Resource not found" — the ID doesn't exist in HA (note: HA returns 400, not 404).
- ok: false + other message — surface the error to the operator.
Reload (optional): After deletion the entity stays in the registry until the next reload. Offer to trigger one:
- Tell the operator to go to HA Developer Tools → Services → automation.reload (or script.reload).
- Do not use validate-apply for this — it would also push the supplied YAML as a new config.

Safety

Always confirm with the operator before deleting. Deletion is immediate and removes the config from HA storage.
Deletion does not check for sensitive entities — the automation is already gone, there is nothing to gate.
After deletion, the automation will no longer fire. The entity_id remains in the registry until reload.

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

4d ago First seen · 40 lines · 37 tokens per session scan A 234286631467

Subscribe to this mod's changes

ha-delete-config is a skill published in the GitHub repository gtapps/claude-code-hermit (74 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 579 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-09-03.

Claude Code Hardware and IoT ai ai-agent anthropic claude claude-code-plugin

kicad-jlcpcb-workflow

Use this skill when the user asks to "design a PCB", "make a board", "build a PCB project", "order from JLCPCB", "create a schematic", "source LCSC parts", "wire up a board", "generate a PCB from a BOM", or any KiCad + JLCPCB workflow. Also use when working with .kicadpro or .kicadpcb files. Phase 1.6 handles project…

BeckhamLabsLLC/kicad-jlcpcb · 145 tokens

especialista-em-engenharia-de-hardware

Especialista em Engenharia de Hardware. Use para design eletrônico, microcontroladores, PCB, firmware embarcado, sinais, energia e prototipagem. Palavras-chave: hardware, eletrônica, microcontrolador, PCB, embarcado, firmware, Arduino.

euwebertdefreitas/ai-skills-for-claude-code · 63 tokens

qector-hardware-engineer

Physical-layer quantum circuits, detector-error-model preparation, qLDPC reasoning, and honest target-device hardware reporting for QECTOR. The bundled library MCP server is app-free; the companion bench server adds DEM inspection, DEM collapse, code-family introspection, and hardware probes (all Provisional).…

GuillaumeLessard/qector-claude-plugin · 103 tokens

ha-delete-config