core: Skill for Claude Code

.claude/skills/ha-quality-scale-verify/SKILL.md

ha-quality-scale-verify is a skill for Claude Code from home-assistant/core. It costs 84 tokens per session (731 once invoked), scanned A, original, Apache-2.0.

A checker for one Home Assistant integration quality-scale rule at a time. The quality scale is Home Assistant’s set of requirements for how integrations should be built and maintained.

In plain words
What is it for?
Use it to verify rules such as configuration flows, unique entity identifiers, or parallel updates for a named integration.
Why use it?
It turns a broad quality requirement into a focused check against the official rule and the integration’s code and configuration.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions subagents.

This is home-assistant/core's own configuration. It tells Claude Code how to work on core itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything core configures →

About the project

Home Assistant is open-source home automation software that lets people control devices and actions locally through a modular system. It is used by home-automation enthusiasts and DIY users, often on a Raspberry Pi or local server; the catalogue entries support operating or developing its integrations and codebase.

home-assistant/core · 90,334 stars · on GitHub · home-assistant.io

Reuse

Borrowing it

Nothing to install: this file belongs to home-assistant/core. 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/home-assistant/core/dev/.claude/skills/ha-quality-scale-verify/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/home-assistant/core

Made for: Claude Code.

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.

agentmods badge for ha-quality-scale-verify

README.md
[![agentmods](https://agentmods.dev/badge/skills/home-assistant/core/ha-quality-scale-verify/github.svg)](https://agentmods.dev/skills/home-assistant/core/ha-quality-scale-verify)
Your own site
<a href="https://agentmods.dev/skills/home-assistant/core/ha-quality-scale-verify"><img src="https://agentmods.dev/badge/skills/home-assistant/core/ha-quality-scale-verify/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.

agentmods 80×15 button for ha-quality-scale-verify

Your own site · 80×15
<a href="https://agentmods.dev/skills/home-assistant/core/ha-quality-scale-verify"><img src="https://agentmods.dev/badge/skills/home-assistant/core/ha-quality-scale-verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 84 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 731 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. Third-party audits
  • Snyk pass 7 Sept 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00084 $0.00731
Opus 5 $0.00042 $0.00365
Sonnet 5 $0.00017 $0.00146
Haiku 4.5 $0.00008 $0.00073

Measured 8d ago against content hash 20a02414096a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

ha-quality-scale-verify 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 8d 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.

.claude/skills/ha-quality-scale-verify/SKILL.md · 53 lines

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.

Verify Quality Scale Rule

You are verifying whether a Home Assistant integration follows a specific quality scale rule. Verify one rule at a time; to check a full tier, verify each of that tier's rules (run in parallel subagents when possible).

1. Fetch rule documentation

Retrieve the official rule documentation from: https://raw.githubusercontent.com/home-assistant/developers.home-assistant/refs/heads/master/docs/core/integration-quality-scale/rules/{rule_name}.md where {rule_name} is the rule identifier (e.g. config-flow, entity-unique-id, parallel-updates).

2. Understand rule requirements

Parse the rule documentation to identify:

  • Core requirements and mandatory implementations
  • Specific code patterns or configurations required
  • Common violations and anti-patterns
  • Exemption criteria (when a rule might not apply)
  • The quality tier this rule belongs to (Bronze, Silver, Gold, Platinum)

3. Analyze the integration code

Examine the integration's codebase at homeassistant/components/<integration domain>, focusing on:

  • manifest.json for quality scale declaration and configuration
  • quality_scale.yaml for rule status (done, todo, exempt)
  • Relevant Python modules based on the rule requirements
  • Configuration files and service definitions as needed

Additional sources:

  • Integration docs: Fetch https://raw.githubusercontent.com/home-assistant/home-assistant.io/refs/heads/current/source/_integrations/<integration domain>.markdown
  • PyPI package info: https://pypi.org/pypi/<package>/json

4. Verification process

  • Check if the rule is marked done, todo, or exempt in quality_scale.yaml
  • If marked exempt, verify the exemption reason is valid
  • If marked done, verify the actual implementation matches the requirements
  • Identify specific files and code sections that demonstrate compliance or violations
  • Consider the integration's declared quality tier when applying rules
  • Look for the exact implementation patterns specified in the rule
  • Check for common mistakes, anti-patterns, edge cases, and error handling requirements
  • Validate that implementations follow Home Assistant conventions

Read the full file on GitHub · 53 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.

  1. 8d ago First seen · 53 lines · 84 tokens per session scan A 20a02414096a

Subscribe to this mod's changes

ha-quality-scale-verify is a skill published in the GitHub repository home-assistant/core (90,334 stars, last pushed today), licensed Apache-2.0. It adds 84 tokens to every session and 731 once invoked, about $0.0004 per session on Opus 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.

Related

Other skills, from other repositories