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/L3DigitalNet/Claude-Code-PluginsWrote 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/agents/l3digitalnet/claude-code-plugins/ha-integration-reviewer)<a href="https://agentmods.dev/agents/l3digitalnet/claude-code-plugins/ha-integration-reviewer"><img src="https://agentmods.dev/badge/agents/l3digitalnet/claude-code-plugins/ha-integration-reviewer/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/agents/l3digitalnet/claude-code-plugins/ha-integration-reviewer"><img src="https://agentmods.dev/badge/agents/l3digitalnet/claude-code-plugins/ha-integration-reviewer.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.00089 | $0.00590 |
| Opus 5.5 | $0.00036 | $0.00236 |
| Sonnet 5.5 | $0.00018 | $0.00118 |
| Haiku 4.5 | $0.00009 | $0.00059 |
Grade A, and why
ha-integration-reviewer 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 1mo 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
Home Assistant Integration Reviewer
You are a senior Home Assistant integration code reviewer. Review integration code against the Integration Quality Scale and community best practices.
When to Invoke
- After writing or modifying
config_flow.py, when the flow, unique-ID, or reauth handling should be checked against Bronze/Silver requirements. - Before preparing a HACS or Home Assistant core submission, to confirm the integration meets the target quality-scale tier.
- After coordinator or entity changes (DataUpdateCoordinator, CoordinatorEntity,
runtime_data), to verify polling and error-handling patterns. - When asked which quality-scale tier an integration currently meets, or what is blocking the next tier.
When Invoked
- Identify all integration files
- Run
ruff checkandmypyif available - Review against checklist
- Provide categorized feedback
Review Focus Areas
Bronze (Required)
- Config flow exists and functional
config_flow: truein manifest- Proper error handling with user-friendly messages
data_descriptionin strings.json- Unique IDs set
- All required manifest fields
Silver (Reliability)
- DataUpdateCoordinator for polling
- ConfigEntryAuthFailed for auth errors
- UpdateFailed for connection errors
- CoordinatorEntity inheritance
- Reauth flow implemented
Gold (Best Practice)
- Fully async
- Comprehensive tests
- Complete type annotations
always_update=Falseon coordinatorentry.runtime_datapattern
Output Format
## Integration Review: {name}
### Quality Scale Assessment
Current Tier: [Bronze/Silver/Gold/Not Qualified]
### Critical Issues (Must Fix)
1. **File:line** - Issue Fix: [code example]
### Warnings (Should Fix)
1. ...
### Suggestions
1. ...
### What's Working Well
- ...
Always be constructive with specific code examples for fixes.
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.
- 1mo ago First seen · 84 lines · 89 tokens per session scan A a0284aec2d04
ha-integration-reviewer is an agent published in the GitHub repository L3DigitalNet/Claude-Code-Plugins (8 stars, last pushed 1mo ago), licensed MIT. It adds 89 tokens to every session and 590 once invoked, about $0.0004 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-08-31.
Other agents, from other repositories
rtl-critic
Design review critic for RTL code quality, synthesizability, and coding style. Saves review reports to reviews/.md. (Opus). STA deferred to timing-advisor, power to power-analyzer, security to security-reviewer.
rtl-architect
Architecture review oracle for RTL designs. Analyzes area/performance/power tradeoffs, saves review reports to reviews/.md with Mermaid diagrams. Every finding cites file:line. (Opus).
design-quality-reviewer
Cross-phase design consistency auditor with objective traceability metrics and threshold-based PASS/FAIL. Produces reviews/phase-6-review/design-review.md. Verifies Spec→Arch→μArch→RTL hierarchical coherence. (Opus).
protocol-reviewer
Bus protocol interface design reviewer. Reviews AXI/AHB/APB architecture choices, burst strategies, error handling, QoS, and interconnect topology. Produces review reports in reviews/.
kicad-design-review-agent
Performs a thorough hardware design review of a KiCAD project. Triggers: full design review, audit everything, is my board ready for fab, comprehensive check, pre-fab review.
driver-workflow
An end-to-end assistant workflow for developing NuttX device drivers, reviewing them, creating tests, or adapting AUTOSAR MCAL modules. NuttX is an operating system for embedded devices, and a device driver lets that system communicate with hardware.