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 agentmods add skills/magnusoverli/opencode/home-assistant-developmentnpx skills add magnusoverli/opencode --skill home-assistant-developmentgit clone --depth 1 https://github.com/magnusoverli/opencodeWhat 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 | $0.00089 | $0.01280 |
| Opus 5 | $0.00044 | $0.00640 |
| Sonnet 5 | $0.00018 | $0.00256 |
| Haiku 4.5 | $0.00009 | $0.00128 |
Grade A, and why
home-assistant-development 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 3d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developing for Home Assistant
This is code, not configuration. The consent rules still apply, and so does the
rule that .storage/ and the other internal directories are off-limits.
Custom integrations
A custom integration lives at custom_components/<domain>/ and needs at least
manifest.json and __init__.py. manifest.json carries domain, name,
version, documentation, dependencies, codeowners, requirements, and
iot_class — Home Assistant refuses to load an integration whose manifest is
incomplete, and the error appears only in the log.
Points worth checking against the running version, because they change:
- Config-flow vs YAML setup — new integrations are config-flow only.
async_setup_entry/async_unload_entryand the coordinator pattern (DataUpdateCoordinator) for anything that polls.- Entity naming:
_attr_has_entity_nameand_attr_nameinteract in a way that has changed more than once. hass.config_entries.async_forward_entry_setups— the plural, awaited form.
Any change under custom_components/ needs a full Home Assistant restart.
There is no reload for integration code. Say so, and ask.
Read the current developer documentation rather than recalling API shapes —
get_integration_docs covers user-facing configuration, and
https://developers.home-assistant.io is the reference for the code side.
Native LLM tool providers
Home Assistant has a native llm platform: Core and custom integrations expose
curated tools through <integration>/llm.py and register an LLM API. Newer
builds also serve those APIs over native MCP at /api/mcp/<API ID> — the
built-in Assist API is /api/mcp/assist.
get_ha_llm_development_guidereturns the upstream references and a starter template for writing anllm.pyprovider. Use it before writing one.get_agent_capabilities(or theha://agent/capabilitiesresource) reports whether the running instance actually has the nativellmcomponent and which native MCP endpoints answer.- This add-on cannot register tools with Home Assistant's
llmplatform. Registration is internal to integrations and custom integrations. What the add-on can do is consume a configured native LLM API over native MCP, which is what the optionalhomeassistant_nativeMCP server does. - Native tools are curated by Home Assistant and are the better choice for
requests that fit the configured API. The add-on's own MCP server is for
configuration editing, safe writes, validation, admin and development
workflows, screenshots, updates, ESPHome,
hab, Zigbee, and documentation lookup.
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.
- 3d ago First seen · 108 lines · 89 tokens per session scan A 5b75cba48510
home-assistant-development is a skill published in the GitHub repository magnusoverli/opencode (362 stars, last pushed 3d ago), licensed Unlicense. It adds 89 tokens to every session and 1,280 once invoked, about $0.0004 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
add-macos-statusbar
Add a macOS menu bar status indicator for NanoClaw. Shows a bolt icon with a green/red dot indicating whether NanoClaw is running, with Start, Stop, and Restart controls. macOS only.
cli-anything-3mf
3MF mesh geometry editor — detect and resize cylindrical holes, repair meshes, compare 3D printing files. Works with BambuStudio and PrusaSlicer 3MF files.
platform-port
Guide porting FastLED to new MCU platforms, including int.h types, clockless drivers, SPI implementations, and platform detection. Use when adding support for a new microcontroller family or board.
doca-compress
Use this skill for hands-on DOCA Compress programming on a BlueField DPU, ConnectX NIC, or host with DOCA — enabling compress-deflate, decompress-deflate, decompress-lz4-stream, or decompress-lz4-block tasks on a docacompress context (the hardware supports DEFLATE both directions plus LZ4 decompress; LZ4 encode is NOT…
pcbway
PCBWay PCB fabrication and assembly — turnkey/consigned assembly, design rules, ordering workflow. Alternative to JLCPCB for manufacturing. Use with KiCad. Use this skill when the user mentions PCBWay, needs turnkey assembly (PCBWay sources parts by MPN), has parts not available on LCSC, needs assembled boards with…
anta-validation
Validate Arista EOS network state with structured pass/fail verdicts using ANTA. Use for "is this switch healthy", "did my change break anything", "verify BGP/interfaces/hardware are correct", "run a health check on this device". Read-only. A test for a feature the device does not run reports notapplicable — never a…