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.
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.
curl -O https://raw.githubusercontent.com/alexbelgium/hassio-addons/master/.github/prompts/issue-execute-plan.mdgit clone --depth 1 https://github.com/alexbelgium/hassio-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/commands/alexbelgium/hassio-addons/issue-execute-plan)<a href="https://agentmods.dev/commands/alexbelgium/hassio-addons/issue-execute-plan"><img src="https://agentmods.dev/badge/commands/alexbelgium/hassio-addons/issue-execute-plan.svg" alt="Measured on agentmods" 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.00000 | $0.00994 |
| Opus 5 | $0.00000 | $0.00497 |
| Sonnet 5 | $0.00000 | $0.00199 |
| Haiku 4.5 | $0.00000 | $0.00099 |
Grade A, and why
issue-execute-plan 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute an approved plan — tier 3
@alexbelgium reviewed an AI-written plan and approved it. Your job is to carry that plan out and open a pull request. The plan was already accepted, so do not re-litigate it — execute it. The only judgement left to you is whether the plan still applies to the current source.
Read:
/tmp/ai-exec/plan.md— the approved plan (root cause, the exact files and diff, verification, risk). This is your spec./tmp/ai-exec/issue.json— the issue it fixes (forCloses #<n>and context).
Hard limits (identical to the fix sweep; only limit 1 is machine-enforced)
- Never modify
.github/or.templates/. Repo-wide infrastructure. config.yamlis yours to edit, except the upstream part ofversion; never editupdater.json—addons_updaterowns both. (There is noupstream:key inconfig.yaml.) You must still bump the local patch counter, or Supervisor never offers the rebuild and the fix ships inert. Readupdater.jsonto find the boundary — you cannot tell it fromversionalone, since upstream versions here run to four or five components. WithU=upstream_version: ifversionequalsU, append.1(sonarr4.0.19.3001->4.0.19.3001.1); if it isU+.+ digits, increment those digits (radarr6.3.0.10514.1->6.3.0.10514.2); anything else — noupdater.json, drifted version, LSIO tag, date, nightly — leaveversionalone and say so in the pull request body. A dot, never a hyphen.- One add-on, one branch:
ai-fix/<addon>-<issue-number>. - Never merge, never close the issue, never enable auto-merge. Open the
pull request ready for review — CI (
onpr_check-pr.yaml) validates it, a human ships it.
Do this in order
- Apply the plan. Make exactly the edits it describes. Match surrounding
style (bash / Dockerfile; conventions vary per add-on). Run
shellcheckon any shell you change. Add aCHANGELOG.mdentry in the add-on's format.
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 · 69 lines · 0 tokens per session scan A cdd020e52026
issue-execute-plan 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 994 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.
Other commands, from other repositories
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
commit-claude-config
Version the Solana AI Kit config in git (un-ignores .claude/, CLAUDE.md, .mcp.json, .gitmodules and commits them).
feat
Quick feature commit. Use for new feature, add feature, implement, create new.
step6-ship
Pipeline Step 6 — Ship the completed phase: commit, update roadmap, capture postmortem, optionally push and create PR.
triage-github
Scan GitHub repos for activity, generate a summary, and create actionable GTD tasks.