agentmods.dev

ha-delete-config

ha-delete-config is a skill for Claude Code from gtapps/hermitd. It costs 37 tokens per session (569 once invoked), scanned A, original, MIT.

A Home Assistant tool for deleting an automation or script through its REST API, with operator confirmation and a result check. Home Assistant is software for controlling smart-home devices and routines.

In plain words
What is it for?
Use it to identify, preview, and delete a specific Home Assistant automation or script.
Why use it?
It helps remove the correct configuration while warning when a YAML-defined item cannot be deleted through the API and showing that deletion cannot be undone through the command line.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the hermitd-homeassistant plugin — 18 skills, 3 agents shipped together

not rated 79repo +5 today A scan 37 tokens original MIT

Good fit Use it to identify, preview, and delete a specific Home Assistant automation or script.

Compare 6 skills from other repositories ↓
View source ↗ gtapps/hermitd hermitd.dev
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/hermitd
Claude Code
/plugin install hermitd-homeassistant

Made for: Claude Code.

Or install hermitd-homeassistant, 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.

agentmods badge for ha-delete-config

README.md
[![agentmods](https://agentmods.dev/badge/skills/gtapps/hermitd/ha-delete-config/github.svg)](https://agentmods.dev/skills/gtapps/hermitd/ha-delete-config)
Your own site
<a href="https://agentmods.dev/skills/gtapps/hermitd/ha-delete-config"><img src="https://agentmods.dev/badge/skills/gtapps/hermitd/ha-delete-config/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.

agentmods 80×15 button for ha-delete-config

Your own site · 80×15
<a href="https://agentmods.dev/skills/gtapps/hermitd/ha-delete-config"><img src="https://agentmods.dev/badge/skills/gtapps/hermitd/ha-delete-config.svg" alt="Reviewed on agentmods" width="80" 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 569 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00037 $0.00569
Opus 5.5 $0.00015 $0.00228
Sonnet 5.5 $0.00007 $0.00114
Haiku 4.5 $0.00004 $0.00057

Measured 11d ago against content hash 4c49ac4a2883, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-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 11d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

plugins/hermitd-homeassistant/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

  1. 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.

  2. Preview: Show the target details (entity_id, id, friendly_name, state). This action cannot be undone via CLI.

  3. 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.

  4. 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.

  5. 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.

  1. 11d ago First seen · 40 lines · 37 tokens per session scan A 4c49ac4a2883

Subscribe to this mod's changes

ha-delete-config is a skill published in the GitHub repository gtapps/hermitd (79 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 569 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-10-02.

Claude CodeHardware and IoTaiai-agentanthropicclaudeclaude-code-plugin
Related

Other skills, from other repositories

volt-ota

Produce a complete OTA update system design — partition layout, update flow, rollback conditions, validation checks, fleet management approach, failure modes and recovery. Use when asked about "OTA updates", "firmware updates over the air", "how do I update devices in the field", "OTA strategy", or "remote firmware…

tonone-ai/tonone · 70 tokens

volt-firmware

Produce a complete firmware architecture spec for a described device — layer diagram, module responsibilities, HAL interface definitions, key state machines, RTOS decision. Use when asked to "design firmware architecture", "plan embedded firmware", "architect an IoT device", "how should I structure this firmware", or…

tonone-ai/tonone · 76 tokens

volt-power

Power management audit — analyze sleep modes, wake sources, power state machines, radio duty cycles, and battery life estimates. Use when asked to "audit power usage", "optimize battery life", "review power management", "why is my battery draining", "power budget analysis", or "sleep mode review".

tonone-ai/tonone · 65 tokens

volt-driver

Build a device driver or protocol handler — I2C sensors, BLE services, MQTT clients, SPI peripherals with interrupt-driven I/O and clean HAL abstraction. Use when asked to "write a driver", "I2C device", "BLE service", "MQTT client", or "sensor integration".

tonone-ai/tonone · 63 tokens

volt-recon

Firmware reconnaissance for takeover — inventory the MCU, peripherals, RTOS, protocols, OTA, power management, and assess code quality with risk flags. Use when asked to "understand this firmware", "device inventory", or "embedded assessment".

tonone-ai/tonone · 52 tokens

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. Handles project setup…

BeckhamLabsLLC/kicad-jlcpcb · 140 tokens