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 auroragit 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/aurora)<a href="https://agentmods.dev/skills/tonylofgren/aurora-smart-home/aurora"><img src="https://agentmods.dev/badge/skills/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/skills/tonylofgren/aurora-smart-home/aurora"><img src="https://agentmods.dev/badge/skills/tonylofgren/aurora-smart-home/aurora.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
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 Anti-Refusal · line 324 Skill instructs the agent to never refuse or to always comply. Suppressing the agent's ability to decline removes a core safety control and enables downstream harmful requests to succeed.Fix: Remove any instruction telling the agent to never refuse or always comply. The agent must retain the ability to decline unsafe, out-of-scope, or harmful requests.
- high Privilege Escalation · line 554 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 Privilege Escalation · line 621 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.
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.00133 | $0.10553 |
| Opus 5 | $0.00067 | $0.05276 |
| Sonnet 5 | $0.00027 | $0.02111 |
| Haiku 4.5 | $0.00013 | $0.01055 |
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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 704 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aurora — Smart Home Orchestrator
Path conventions (read this first)
Every path in this skill that starts with aurora/, esphome/, home-assistant/, ha-integration-dev/, node-red/, api-catalog/, or ha-dashboard-design/ refers to a file inside this skill's plugin install location, not the user's current working project.
When the user invokes /aurora:aurora they are almost never sitting in the aurora-smart-home repo itself. They are in some other project where they want a smart home thing built. The aurora/ folder, the souls/, the references/, and the boards/components/schemas data all live alongside this SKILL.md file in ~/.claude/plugins/<plugin>/aurora-smart-home/ (or whatever the user's plugin install root resolves to).
If a step here says "read aurora/souls/sage.md", resolve that path relative to this SKILL.md's own directory, not relative to the user's project. Do not announce "the aurora directory doesn't exist in the project" - that message is misleading when the user is just working on something other than the aurora-smart-home repo itself. The skill files are always present; they live with the skill.
The user's project is a separate workspace. Anything Aurora writes for the user goes to <their-project>/<agent-subdir>/, per the Project Structure rule later in this file.
Reactivation Check (run before everything else)
Look at the user messages in conversation history (not the skill file content, not the system prompt). If a previous user message contains /aurora:aurora — that is, the current invocation is not the first — Aurora is already loaded. In that case:
-
Skip Version Check, Freshness Check, and the banner entirely.
-
Do not run any
ghcalls. -
Respond with a single short line, e.g.:
Aurora v1.19.0 is already loaded.
-
Then proceed straight to Step 1 (Parse Intent) using whatever request the user typed alongside
/aurora:aurora. If the user typed nothing alongside it, ask the opening question once:
What ships with it
60 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.
- evals/evals.json 8.9 KB
- evals/golden-baseline.json 1.2 KB
- evals/grade.py 5.8 KB runs code
- evals/README.md 6.6 KB
- evals/run_evals.py 4.5 KB runs code
- recipes/_index.md 3.7 KB
- recipes/_recipe-format.md 3.0 KB
- recipes/button-scenes.md 2.0 KB
- recipes/co2-monitor.md 2.2 KB
- recipes/daylight-lights.md 2.4 KB
- recipes/dc-power-monitor.md 2.5 KB
- recipes/energy-dashboard.md 1.9 KB
- recipes/fridge-freezer-monitor.md 2.2 KB
- recipes/greenhouse.md 2.4 KB
- recipes/motion-light.md 2.5 KB
- recipes/notification-hub.md 2.1 KB
- recipes/presence-routine.md 2.0 KB
- recipes/room-presence.md 2.3 KB
- recipes/smart-thermostat.md 2.3 KB
- recipes/vacation-mode.md 2.0 KB
- recipes/weather-station.md 2.4 KB
- references/boards/esp32/esp32-c3-mini.json 4.3 KB
- references/boards/esp32/esp32-c6-devkit.json 4.3 KB
- references/boards/esp32/esp32-devkit-v1.json 4.8 KB
- references/boards/esp32/esp32-h2-devkit.json 4.3 KB
- references/boards/esp32/esp32-s2-mini.json 4.7 KB
- references/boards/esp32/esp32-s3-devkitc-1.json 4.8 KB
- references/boards/esp8266/d1-mini.json 4.5 KB
- references/boards/module/esp32-c3-mini-1.json 4.0 KB
- references/boards/module/esp32-c6-mini-1.json 4.2 KB
- references/boards/module/esp32-s3-wroom-2.json 4.8 KB
- references/boards/rp/pico-2-w.json 4.4 KB
- references/boards/rp/pico-w.json 4.4 KB
- references/boards/smart-home/shelly-plus-1.json 3.9 KB
- references/boards/smart-home/shelly-plus-2pm.json 4.1 KB
- references/boards/smart-home/sonoff-basic-r3.json 4.0 KB
- references/boards/smart-home/sonoff-mini-r3.json 3.9 KB
- references/boards/special/heltec-wifi-lora32-v3.json 4.6 KB
- references/boards/special/lilygo-t-display-s3.json 4.6 KB
- references/boards/special/m5stack-atom-lite.json 4.1 KB
- references/boards/special/m5stack-core-basic.json 4.5 KB
- references/boards/special/xiao-esp32-c3.json 4.4 KB
- references/boards/special/xiao-esp32-c6.json 4.4 KB
- references/boards/special/xiao-esp32-s3.json 4.7 KB
- references/check-in-format.md 1.2 KB
- references/components/air-quality/mh-z19b.json 1.7 KB
- references/components/air-quality/pms5003.json 2.3 KB
- references/components/air-quality/scd40.json 2.1 KB
- references/components/air-quality/sgp40.json 2.5 KB
- references/components/light/bh1750.json 2.2 KB
- references/components/moisture/capacitive-soil-v1.2.json 1.7 KB
- references/components/motion/ld2410.json 1.8 KB
- references/components/motion/pir-am312.json 1.7 KB
- references/components/power/ina219.json 2.4 KB
- references/components/temperature/aht20.json 2.1 KB
- references/components/temperature/bme280.json 2.1 KB
- references/components/temperature/bmp280.json 2.1 KB
- references/components/temperature/dht22.json 1.9 KB
- references/components/temperature/ds18b20.json 1.7 KB
- references/components/temperature/ntc-thermistor-10k.json 1.9 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.
- 10d ago First seen · 704 lines · 133 tokens per session scan A f487a8624e76
aurora is a skill published in the GitHub repository tonylofgren/aurora-smart-home (104 stars, last pushed 5d ago), licensed MIT. It adds 133 tokens to every session and 10,553 once invoked, about $0.0007 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 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.
contributors-update
Find merged PR authors missing from README and update the contributors list after approval.
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 ".