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/commands/tonylofgren/aurora-smart-home/aurora)<a href="https://agentmods.dev/commands/tonylofgren/aurora-smart-home/aurora"><img src="https://agentmods.dev/badge/commands/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/commands/tonylofgren/aurora-smart-home/aurora"><img src="https://agentmods.dev/badge/commands/tonylofgren/aurora-smart-home/aurora.svg" alt="Reviewed on agentmods" width="80" 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.00051 | $0.00232 |
| Opus 5 | $0.00026 | $0.00116 |
| Sonnet 5 | $0.00010 | $0.00046 |
| Haiku 4.5 | $0.00005 | $0.00023 |
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 9d 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
Read and follow the aurora/SKILL.md file that lives in this Aurora plugin's install directory - the same plugin directory that contains this commands/aurora.md file. Resolve the path relative to this command file's own location inside ~/.claude/plugins/<plugin>/aurora-smart-home/, NOT relative to the user's current working directory. The user is almost always sitting in a different project (where they want a smart home thing built) and that project will not contain an aurora/ folder. If you cannot find aurora/SKILL.md next to this command file, the Aurora plugin install is broken - say so directly rather than offering to create the file in the user's working project.
Once aurora/SKILL.md is loaded, start with the banner display and the opening question per the instructions in that file.
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.
- 9d ago First seen · 8 lines · 51 tokens per session scan A 9308adf73c65
aurora is a command published in the GitHub repository tonylofgren/aurora-smart-home (104 stars, last pushed 4d ago), licensed MIT. It adds 51 tokens to every session and 232 once invoked, about $0.0003 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-08-30.
Other commands, from other repositories
scan
Discover Reolink devices on the local network (UDP broadcast, 2s).
devices
List registered Reolink aliases (from /.config/reolink-cli/aliases.toml).
status
Reolink observability dashboard (fleet + gateway + monitor + cache + recent events).
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
device-info
A device-scanning command that identifies the connected chip and its VID:PID hardware identifiers. It also provides suggestions for the driver needed to use the device.
stm32-setup
Set up STM32 MCP documentation server - installs dependencies and configures your project.