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 tonylofgren/aurora-smart-home --skill node-redgit clone --depth 1 https://github.com/tonylofgren/aurora-smart-homeWrote 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/tonylofgren/aurora-smart-home/node-red)<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="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.1 | $0.00076 | $0.03161 |
| Opus 5 | $0.00038 | $0.01580 |
| Sonnet 5 | $0.00015 | $0.00632 |
| Haiku 4.5 | $0.00008 | $0.00316 |
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 7d 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); 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)
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.
- CHEATSHEET.md 4.7 KB
- INSTALLATION.md 6.8 KB
- LICENSE 1.0 KB
- PROMPT-IDEAS.md 9.8 KB
- README.md 2.7 KB
- references/automation-patterns.md 9.7 KB
- references/context-storage.md 7.4 KB
- references/cookbook.md 11 KB
- references/core-concepts.md 6.5 KB
- references/dashboard-2.md 5.5 KB
- references/error-handling.md 7.7 KB
- references/external-apis.md 11 KB
- references/flow-organization.md 10 KB
- references/function-nodes.md 8.1 KB
- references/ha-action-nodes.md 7.9 KB
- references/ha-advanced-nodes.md 11 KB
- references/ha-entity-nodes.md 10.0 KB
- references/ha-setup.md 4.8 KB
- references/ha-state-nodes.md 8.8 KB
- references/ha-trigger-nodes.md 9.3 KB
- references/jsonata.md 6.5 KB
- references/message-handling.md 9.9 KB
- references/mqtt-integration.md 8.6 KB
- references/node-reference.md 7.7 KB
- references/node-types.md 9.5 KB
- references/performance.md 6.1 KB
- references/popular-apis.md 8.6 KB
- references/security.md 10 KB
- references/state-machines.md 7.4 KB
- references/subflows.md 7.6 KB
- references/troubleshooting-flowcharts.md 19 KB
- references/troubleshooting.md 7.0 KB
- templates/advanced-motion-light.json 7.6 KB
- templates/appliance-tracker.json 5.6 KB
- templates/basic-motion-light.json 3.6 KB
- templates/climate-control.json 6.1 KB
- templates/energy-monitor.json 5.7 KB
- templates/notification-router.json 5.5 KB
- templates/presence-detection.json 5.9 KB
- templates/README.md 2.6 KB
- templates/scene-controller.json 7.2 KB
- templates/security-alerts.json 6.3 KB
- templates/subflow-debounce.json 3.4 KB
- templates/subflow-notification.json 8.2 KB
- USAGE-GUIDE.md 7.2 KB
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.
- 7d ago First seen · 396 lines · 76 tokens per session scan A 9f395d902a49
Node-RED is a skill published in the GitHub repository tonylofgren/aurora-smart-home (104 stars, last pushed yesterday), licensed MIT. It adds 76 tokens to every session and 3,161 once invoked, about $0.0004 per session on Opus 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.
Other skills, from other repositories
bat-story-eval
Compare MCP tool behavior between target and baseline versions using pre-built and custom stories with diff-based triage.
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.
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.
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…
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 ".
contributors-update
Find merged PR authors missing from README and update the contributors list after approval.