Instructions for building Node-RED visual automation flows that control Home Assistant, a platform for managing smart-home devices.

Use it to create trigger-based automations, call Home Assistant services, run functions, store context, and build timer or error-handling patterns.

It helps produce flows with current node names, required files, error handling, and recovery guidance so the automation can be installed and maintained.

Node-RED — Skill for Claude Code by tonylofgren/aurora-smart-home

Install

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.

Any agent

npx skills add tonylofgren/aurora-smart-home --skill node-red

Clone the repo

git clone --depth 1 https://github.com/tonylofgren/aurora-smart-home

Made for: Claude Code.

Or install aurora, the plugin that ships this one along with the rest of its 6 skills, 1 command.

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/tonylofgren/aurora-smart-home/node-red/github.svg)](https://agentmods.dev/skills/tonylofgren/aurora-smart-home/node-red)

Your own site

<a href="https://agentmods.dev/skills/tonylofgren/aurora-smart-home/node-red"><img src="https://agentmods.dev/badge/skills/tonylofgren/aurora-smart-home/node-red/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/tonylofgren/aurora-smart-home/node-red"><img src="https://agentmods.dev/badge/skills/tonylofgren/aurora-smart-home/node-red.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 3,161 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 3 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

high Privilege Escalation · line 39
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
high Anti-Refusal · line 338
Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.

Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
medium Data Exfiltration · line 235
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.

How audits are shown

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.00076	$0.03161
Opus 5.5	$0.00030	$0.01264
Sonnet 5.5	$0.00015	$0.00632
Haiku 4.5	$0.00008	$0.00316

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

Security

Grade A, and why

Node-RED scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

const response = await axios.get(msg.url);

node-red/SKILL.md · 396 lines

How it starts

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

Node-RED for Home Assistant

Build Node-RED flows using node-red-contrib-home-assistant-websocket nodes (v0.80+).

Requirements: Node-RED 4.x (Node.js 18+), Home Assistant 2024.3.0+.

The Iron Law

USE CURRENT NODE NAMES - NEVER OUTDATED ONES

The node-red-contrib-home-assistant-websocket package has renamed several nodes. Using old names produces broken flows that silently fail.

Delivery Contract (read first, applies to every output)

Every flow ships as files in a project folder on disk. Chat output is not delivery. A flow JSON pasted in chat is not a delivered flow. Create <project-slug>/ (or write into the existing project folder in a multi-agent build), write the flow JSON under node-red-flows/, and write a README.md per Iron Law 3 in ../aurora/souls/river.md. README sections follow ../aurora/references/deliverables/manual-format.md: What this does, Installation, Troubleshooting, Recovery. No chat-only output option.

The Process

User request
    │
    ▼
HA server config node exists in Node-RED?
    │ no ─────────────────────────┐
    │ yes                          ▼
    │                       Set up `server` config first
    │                       (URL, access token, allow self-signed if needed)
    │                              │
    ▼ ◀────────────────────────────┘
Pick trigger node (current names only — see table below)
    │
    │  time-based?    ──▶  inject (time) or trigger-state with cron
    │  state-change?  ──▶  trigger-state OR events:state
    │  event?         ──▶  events:all (filtered by event_type)
    │  external?      ──▶  http in (webhook) / mqtt in
    │
    ▼
Add filter/condition (current-state, switch, template)
    │
    ▼
Pick action node (current names only)
    │
    │  call HA service?     ──▶  call-service (`action`, not `service`)
    │  set entity state?    ──▶  call-service light.turn_on / etc.
    │  send HTTP?           ──▶  http request
    │  notify?              ──▶  call-service notify.*
    │
    ▼
Battery-drain risk? ──yes──▶ Add throttle/delay (rate-limit msgs/sec)
    │ no
    ▼
Add status indicators (debug node OR catch node for error path)
    │
    ▼
Test in editor with debug node, fix wiring
    │
    ▼
Deploy and verify in HA
    │
    ▼
Document the flow (description on key nodes)

Read the full file on GitHub · 396 lines

Files

What ships with it

45 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 · 396 lines · 76 tokens per session scan A 9f395d902a49

Subscribe to this mod's changes

Node-RED is a skill published in the GitHub repository tonylofgren/aurora-smart-home (109 stars, last pushed 5d ago), licensed MIT. It adds 76 tokens to every session and 3,161 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude Code Hardware and IoT claude-skill esphome hacs home-assistant home-automation

bat-story-eval

Compare MCP tool behavior between target and baseline versions using pre-built and custom stories with diff-based triage.

homeassistant-ai/ha-mcp · 26 tokens

contrib-pr-review

Review a contribution PR for safety, quality, and readiness. Checks for security concerns, test coverage, size appropriateness, and intent alignment. Use when reviewing external contributions.

homeassistant-ai/ha-mcp · 39 tokens

bat-adhoc

Run bot acceptance tests to validate MCP tools work correctly from a real AI agent's perspective. Use when testing PRs, detecting regressions, or verifying tool changes end-to-end with Claude/Gemini CLIs.

homeassistant-ai/ha-mcp · 48 tokens

contributors-update

Find merged PR authors missing from README and update the contributors list after approval.

homeassistant-ai/ha-mcp · 17 tokens

issue-to-pr-resolver

Implement a GitHub issue end-to-end — create a worktree branch, implement the feature with tests, create a draft PR, then iteratively resolve all CI failures and review comments until the PR is clean. Use when you need to fully implement a GitHub issue from start to merge-ready. Triggers on "implement issue", "resolve…

homeassistant-ai/ha-mcp · 85 tokens

my-pr-checker

Manage your own GitHub pull requests — check CI status, inline review comments, PR-level comments, resolve review threads, fix issues, and iterate until all checks pass and threads are resolved. Use for managing your own PRs (not external contributions). Triggers on "check my PR", "check PR", "/my-pr-checker ".

homeassistant-ai/ha-mcp · 75 tokens

Node-RED