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/pr-coderabbit.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/pr-coderabbit)<a href="https://agentmods.dev/commands/alexbelgium/hassio-addons/pr-coderabbit"><img src="https://agentmods.dev/badge/commands/alexbelgium/hassio-addons/pr-coderabbit.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.00642 |
| Opus 5 | $0.00000 | $0.00321 |
| Sonnet 5 | $0.00000 | $0.00128 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
pr-coderabbit 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Address CodeRabbit's review — one-shot
CodeRabbit reviewed an AI-authored pull request. You are checked out on that
PR's branch (ai-fix/<addon>-<issue>). Your job, in a single pass: read
CodeRabbit's feedback and either fix each actionable point or reply saying why
it doesn't apply. This runs once — CodeRabbit re-reviewing your pushed fix will
not trigger you again.
The PR number is in your prompt. Set PR to it.
Gather the feedback
- Review summaries and verdicts:
gh pr view "$PR" --json reviews,title,body,files - Inline (line-level) comments — this is where CodeRabbit's concrete suggestions
live:
gh api "repos/${GITHUB_REPOSITORY}/pulls/${PR}/comments" --paginateEach haspath,line,body, and anid(needed to reply).
Consider only comments authored by coderabbitai[bot]. Ignore its collapsed
"nitpick"/"outside diff" noise unless the point is real.
Hard limits (a workflow step enforces the first)
- Never modify
.github/or.templates/. Repo-wide infrastructure. - Leave
versioninconfig.yamlalone, and never editupdater.json. The rest ofconfig.yamlis fair game. Unlike the fix sweep, you are amending a pull request that has already bumped the local patch counter — one bump covers the whole PR, so incrementing it again here would just churn the diff. - Stay within this PR's scope and branch. Do not open a new PR, do not touch other add-ons, do not merge, do not mark ready/draft.
For each actionable comment
- Fix it when it's a real correctness, safety, or clarity improvement within
scope: make the minimal edit, run
shellcheckon any shell you change, and if behaviour changed update the add-on'sCHANGELOG.mdentry. - Decline it when it's wrong, out of scope, or a style nit that fights the
add-on's conventions: reply to that specific comment with one sentence of
reasoning:
gh api "repos/${GITHUB_REPOSITORY}/pulls/${PR}/comments/<id>/replies" -f body='...'
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 · 53 lines · 0 tokens per session scan A e2e3808c76f7
pr-coderabbit 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 642 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
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.