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.
npx skills add nolte/claude-home-assistant --skill ha-lovelace-solutiongit clone --depth 1 https://github.com/nolte/claude-home-assistantWrote 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/skills/nolte/claude-home-assistant/ha-lovelace-solution)<a href="https://agentmods.dev/skills/nolte/claude-home-assistant/ha-lovelace-solution"><img src="https://agentmods.dev/badge/skills/nolte/claude-home-assistant/ha-lovelace-solution/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/skills/nolte/claude-home-assistant/ha-lovelace-solution"><img src="https://agentmods.dev/badge/skills/nolte/claude-home-assistant/ha-lovelace-solution.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.00208 | $0.02778 |
| Opus 5 | $0.00104 | $0.01389 |
| Sonnet 5 | $0.00042 | $0.00556 |
| Haiku 4.5 | $0.00021 | $0.00278 |
Grade A, and why
ha-lovelace-solution 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HA Lovelace Solution
Spec: spec/claude/ha-lovelace-solution/en.md (EN canonical) / spec/claude/ha-lovelace-solution/de.md (DE translation).
This skill is the front door to the Lovelace/frontend skill family. It does not generate any artifact itself — it decomposes the requirement, plans the combination, and dispatches the owning skills, each of which owns its generation and spec conformance.
Why this is a skill, not an agent
- Plan-before-generate gate — the artifact plan must be presented and explicitly approved before any generation; that human-visible gate is core to the contract and an agent's fire-and-forget shape would lose it.
- Mid-flow interactivity — clarifying questions (JS vs. Lit/TS, tag name, target entity, backend need), plan confirmation, and the "this needs a Python integration backend" decision are per-run dialogues.
- Orchestrator that dispatches other skills — the skill-orchestrates-skill default (see
skill-vs-agent) keeps the entry point in skill form, likeha-automation-solutiondispatching the automation authoring skills. - Counter-dimension considered: the per-artifact generation could run as parallel agents, but the plan approval and the identity threading (card tag → editor/feature, card → command) must stay visible in the user's context; skill wins.
When this skill activates
Use this skill when the user describes a frontend result that likely needs more than one artifact, and should not have to know which frontend skill produces what — e.g. "a custom card for my pump with a visual config editor and a tile feature", "a dashboard strategy plus a badge", "a custom panel backed by a WebSocket command".
When NOT to activate
- a single clear frontend artifact (one card, one editor, one feature, one badge, one strategy, one panel) → let the owning skill activate directly
- the Python custom-integration backend (own device/cloud protocol, config flow, the WebSocket-command host) →
ha-integration-scaffold - deploying/importing into a running HA instance or writing dashboard/resource config → out of scope (generation only)
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.
- 10d ago First seen · 132 lines · 208 tokens per session scan A 5cae78e01ab6
ha-lovelace-solution is a skill published in the GitHub repository nolte/claude-home-assistant (1 stars, last pushed 1mo ago), licensed MIT. It adds 208 tokens to every session and 2,778 once invoked, about $0.0010 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.
Other skills, from other repositories
cache-components
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). PROACTIVE ACTIVATION: Use this skill automatically when working in Next.js projects that have cacheComponents: true in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best…
frontend-code-review
Trigger when the user requests a review of frontend files (e.g., .tsx, .ts, .js). Support both pending-change reviews and focused file reviews while applying the checklist rules.
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.
flutter-development
Cross-platform development with Flutter and Dart for iOS, Android, Web, Desktop, and embedded. Use when building Flutter apps, implementing Material/Cupertino design, or optimizing Dart code.
electron-desktop
Desktop application development with Electron for Windows, macOS, and Linux. Use when building cross-platform desktop apps, implementing native OS features, or packaging web apps for desktop.
generic-react-feature-developer
Guide feature development for React applications with architecture focus. Covers Zustand/Redux patterns, IndexedDB usage, component systems, lazy loading strategies, and seamless integration. Use when adding new features, refactoring existing code, or planning major changes.