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.
git 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/plugins/tonylofgren/aurora-smart-home/aurora)<a href="https://agentmods.dev/plugins/tonylofgren/aurora-smart-home/aurora"><img src="https://agentmods.dev/badge/plugins/tonylofgren/aurora-smart-home/aurora/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/plugins/tonylofgren/aurora-smart-home/aurora"><img src="https://agentmods.dev/badge/plugins/tonylofgren/aurora-smart-home/aurora.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
aurora 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 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.
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.
What it actually says
{
"name": "aurora",
"description": "Aurora Smart Home - skills for Home Assistant, ESPHome, Node-RED, custom integrations, API catalog, and dashboard design",
"source": "./",
"skills": [
"./home-assistant",
"./esphome",
"./ha-integration-dev",
"./node-red",
"./api-catalog",
"./ha-dashboard-design"
],
"commands": [
"./commands"
]
}What it installs
The manifest is a name and a version. 6 skills, 1 command travel with it, and installing the plugin installs all of them — 731 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside marketplace.json#aurora 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.
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 · 16 lines scan A 2a5fa5299927
aurora is a plugin published in the GitHub repository tonylofgren/aurora-smart-home (109 stars, last pushed 5d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.
Other plugins, from other repositories
unifi-access
UniFi Access MCP server — manage door locks, credentials, visitors, and access policies.
unifi-network
UniFi Network MCP server — manage network devices, clients, firewall, VPN, and more.
unifi-protect
UniFi Protect MCP server — manage security cameras, NVR, recordings, and smart detections.
unifi-intelligence
UniFi Intelligence skills: investigate a Network device incident with Protect camera context, and audit area and visitor activity through the cloud worker. Requires the unifi-network and unifi-protect plugins.
reolink-cli
Operate Reolink cameras locally: discover, login, inspect, configure, preview, snapshot, and control PTZ/light/audio/detection/recording.
reolink-cli
Operate Reolink cameras locally via reolink-cli: discover, login, inspect, configure, preview, snapshot, and control PTZ/light/audio/detection/recording.