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-card-preview-addgit 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-card-preview-add)<a href="https://agentmods.dev/skills/nolte/claude-home-assistant/ha-card-preview-add"><img src="https://agentmods.dev/badge/skills/nolte/claude-home-assistant/ha-card-preview-add/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-card-preview-add"><img src="https://agentmods.dev/badge/skills/nolte/claude-home-assistant/ha-card-preview-add.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.00212 | $0.01934 |
| Opus 5 | $0.00106 | $0.00967 |
| Sonnet 5 | $0.00042 | $0.00387 |
| Haiku 4.5 | $0.00021 | $0.00193 |
Grade A, and why
ha-card-preview-add 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 11d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HA Card Preview Add
Spec: spec/claude/ha-card-preview-add/en.md (EN canonical) / spec/claude/ha-card-preview-add/de.md (DE translation).
This skill makes an existing custom card's preview complete and correct, per spec/ha/lovelace-card-preview/en.md. It completes the missing preview pieces (picker preview, editor live preview, the preview property guard, preview correctness) and validates them — it does not scaffold the card (ha-lovelace-card-scaffold) or build the editor (ha-card-editor-add).
Why this is a skill, not an agent
- Human-visible augmentation surface — the user describes the card and reads back the
window.customCardschange, thegetStubConfig, thepreview-property guard, and a conformance report; a skill keeps this on the visible command surface, like the siblingha-card-editor-add. - Mid-flow interactivity — whether a live picker preview is wanted (
preview: true), the demo entity/placeholder for the stub config, and which side-effects to guard are per-run dialogues the user confirms. - Bounded, inline generation — the customCards flag, the
getStubConfig, and the preview guards fit inline; no isolated agent context is needed. - Counter-dimension considered: the audit-then-complete loop could be an agent, but the demo-entity choice and the report belong in the user's working context; skill wins.
When this skill activates
Use this skill to ensure an existing custom card previews completely and correctly — its card-picker gallery tile renders a real live preview, its editor live preview tracks the config, and it behaves correctly while being previewed.
When NOT to activate
- scaffolding a brand-new card →
ha-lovelace-card-scaffold - building the graphical config editor (
getConfigElement/getConfigForm) →ha-card-editor-add - card layout / sizing / grid behaviour →
ha/lovelace-layout-antipatterns - deploying/importing into a running HA instance → out of scope (generation only)
Hard rules
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.
- 11d ago First seen · 94 lines · 212 tokens per session scan A 8d8babc6a4f2
ha-card-preview-add is a skill published in the GitHub repository nolte/claude-home-assistant (1 stars, last pushed 1mo ago), licensed MIT. It adds 212 tokens to every session and 1,934 once invoked, about $0.0011 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.