A command for diagnosing confirmed bugs in a batch of Home Assistant add-ons and deciding when a written fix plan is needed. Home Assistant is software for controlling smart-home devices.

It helps inspect issue batches, identify likely causes, group related work, and prepare safe fixes or plans.

It separates diagnosis from uncertain implementation and limits changes to the add-on wrappers rather than the upstream applications they package.

How alexbelgium/hassio-addons configures GitHub Copilot

About the project

alexbelgium/hassio-addons is a repository of add-ons that extend Home Assistant, the home-automation platform, with additional services and tools. Home Assistant users install these add-ons to expand their systems, and the catalogue entry relates to the repository's own add-on workflow.

alexbelgium/hassio-addons · 2,588 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to alexbelgium/hassio-addons. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/alexbelgium/hassio-addons/master/.github/prompts/issue-fix.md

Clone the repo

git clone --depth 1 https://github.com/alexbelgium/hassio-addons

Made for: GitHub Copilot.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/alexbelgium/hassio-addons/issue-fix.svg)](https://agentmods.dev/commands/alexbelgium/hassio-addons/issue-fix)

Your own site

<a href="https://agentmods.dev/commands/alexbelgium/hassio-addons/issue-fix"><img src="https://agentmods.dev/badge/commands/alexbelgium/hassio-addons/issue-fix.svg" alt="Measured on agentmods" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,363 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00000	$0.02363
Opus 5	$0.00000	$0.01182
Sonnet 5	$0.00000	$0.00473
Haiku 4.5	$0.00000	$0.00236

Measured yesterday against content hash 5e5463520f00, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

issue-fix 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 yesterday.

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.

.github/prompts/issue-fix.md · 186 lines

How it starts

The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Issue fix sweep — tier 2

You are working through a batch of confirmed add-on bugs on alexbelgium/hassio-addons. Each add-on is a thin wrapper around an upstream application. You own the wrapper. You do not own the upstream app.

Read /tmp/ai-fix/batch.json. Work add-on by add-on, not issue by issue — grouping is the point of the batch.

You are the Opus step of the pipeline: the diagnosis and, when a fix is not a sure thing, the written plan. Getting the diagnosis right and being honest about confidence matters more than the number of pull requests you open.

Hard limits

These are not guidelines. Limit 1 is machine-enforced — a workflow step checks every pull request you open and blocks and flags anything that violates it. The rest are on you: nothing checks them, so breaking one ships silently.

Never modify .github/ or .templates/. Those are inherited by every add-on in the repo. A change there is a 100-add-on incident, not a fix.
config.yaml is yours to edit, with one carve-out. Never change the upstream part of version — the portion that tracks the upstream release — and never edit updater.json at all. The addons_updater job owns both, and editing them causes merge conflicts you will not be around to resolve. (There is no upstream: key in config.yaml; upstream tracking lives in updater.json as upstream_repo / upstream_version.)

The local patch counter is a different thing and you must bump it. When you change any file in an add-on, version must change too — otherwise Supervisor never offers the rebuild, the add-on keeps running the old image, and your fix ships inert: merged, doing nothing, with the issue looking closed. That is worse than not fixing it at all.

You cannot tell the counter from version alone — read updater.json. Upstream versions in this repo have anywhere from one to five components, so a trailing .1234 is just as likely to belong to upstream as to be a local counter. updater.json's upstream_version is the authority. Let U be that value, and compare:

Read the full file on GitHub · 186 lines

Changes

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.

yesterday First seen · 186 lines · 0 tokens per session scan A 5e5463520f00

Subscribe to this mod's changes

issue-fix is a command published in the GitHub repository alexbelgium/hassio-addons (2,588 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,363 tokens. 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-07.

Debugging Project management addons haos hassio hassio-addons home-assistant homeassistant

bug-report

Draft a bug report issue for lean4-skills.

cameronfreer/lean4-skills · 13 tokens

triage

Query open Node bugs, classify by priority and sub-team, suggest assignments, and generate a triage summary.

openshift-eng/ai-helpers · 21 tokens

speckit.companion.doctor

Report on a spec's run health — unfinished steps, unjournaled tasks, step bleed, drift you can judge, a step that closed having verified nothing, a step that closed without the file it promised, and why completion did not land (read-only, retroactive, never halts).

alfredoperez/speckit-companion · 59 tokens

hassio-addons: Command for GitHub Copilot