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/kellerza/hass-addonsWrote 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/rules/kellerza/hass-addons/synced-addons)<a href="https://agentmods.dev/rules/kellerza/hass-addons/synced-addons"><img src="https://agentmods.dev/badge/rules/kellerza/hass-addons/synced-addons/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/rules/kellerza/hass-addons/synced-addons"><img src="https://agentmods.dev/badge/rules/kellerza/hass-addons/synced-addons.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.00616 | $0.00616 |
| Opus 5.5 | $0.00246 | $0.00246 |
| Sonnet 5.5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
synced-addons 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 12d 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
Add-on repository layout (kellerza/hass-addons)
This repo aggregates Home Assistant add-ons. Some folders are maintained here; others are
CI-mirrored from upstream repos by .github/workflows/sync-remotes.yml and will have any manual
edits overwritten on the next sync.
Do NOT hand-edit — CI-synced mirrors
These folders are copied verbatim from another repo. Fix the problem in the source repo, not here:
hass-addon-sunsynk-edge/,hass-addon-sunsynk-multi/,hass-addon-mbusd/— synced fromkellerza/sunsynk. Edit those add-ons in thesunsynkrepo (per its own rules: edge is the dev add-on and Docker build source; multi is the stable/image-only release add-on).Dockerfileandrootfs/are stripped from both folders on sync (image-only mirrors).hass-addon-sma-em-edge/— synced fromkellerza/hassio-sma-em(sma-em-dev; build source). Theslugis rewritten by CI; don't fix it here.Dockerfileandrootfs/are stripped on sync (image-only mirror).
If a task would touch any of the above, redirect: state that the folder is a sync target and the
change belongs in the upstream repo (or in sync-remotes.yml if the sync logic itself is wrong).
Maintained here
Manual work is welcome on the repo's own add-ons and their Python:
hass-addon-control-group/+src/ha_addon_control_group/hass-addon-esp/+src/ha_addon_esp/hass-addon-qsusb64/+src/ha_addon_qsusb64/hass-addon-git-push/(shell/Docker only)src/ha_addon/— shared HA API helpers (ha_api/) used across add-ons.
Pattern: add-on packaging (config.yaml, translations/, Dockerfile, rootfs/ s6 services)
lives in the hass-addon-* folder; behaviour lives in the matching src/ha_addon_* package.
Keep Supervisor options in sync between an add-on's config.yaml, its translations/en.yaml, and
the options.py of its src package.
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.
- 12d ago First seen · 43 lines · 616 tokens per session scan A f87cea68fe6a
synced-addons is a cursor rule published in the GitHub repository kellerza/hass-addons (9 stars, last pushed 3d ago), licensed Apache-2.0. It adds 616 tokens to every session, about $0.0025 per session on Opus 5.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-10-02.
Other cursor rules, from other repositories
git-conventions
Git workflow, conventional commits, and merge policy.
rebase-only-merged-agents
When rebasing after a merge, only rebase the agents whose branches you just merged. Do not rebase agents that are still running.
git-workflow
Rules for git operations, commit strategy, and GitHub CLI usage.
release-checklist
What to update with each code change or version release.
git-workflow
Git commit format and PR process - conventional commits.
branching-merging-strategy
This is a set of instructions to the AI Assistant for branching and merging strategy.