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-sizing-determinegit 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-sizing-determine)<a href="https://agentmods.dev/skills/nolte/claude-home-assistant/ha-card-sizing-determine"><img src="https://agentmods.dev/badge/skills/nolte/claude-home-assistant/ha-card-sizing-determine/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-sizing-determine"><img src="https://agentmods.dev/badge/skills/nolte/claude-home-assistant/ha-card-sizing-determine.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.00222 | $0.02583 |
| Opus 5 | $0.00111 | $0.01291 |
| Sonnet 5 | $0.00044 | $0.00517 |
| Haiku 4.5 | $0.00022 | $0.00258 |
Grade A, and why
ha-card-sizing-determine 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HA Card Sizing Determine
Spec: spec/ha/card-panel-sizing/en.md (EN canonical) / spec/ha/card-panel-sizing/de.md (DE translation). This skill operationalises that decision procedure; it does not restate it — read the spec for the field reference, the .fit-rows mechanics, the source citations, and the canonical card examples.
Why this is a skill, not an agent
- Mid-flow interactivity — the content-shape classification (content-dependent vs. deterministic) and the determined declaration are approved by the user before the card is patched; that approval gate is the load-bearing dimension and belongs on the visible command surface.
- Output flows back to the main conversation — the determined
getGridOptions/getCardSizevalues and the patch are read back inline, without a structured report boundary; the caller keeps working in the same context. - Bounded inline generation with a hand-off — determination plus patching two small callbacks fits inline; where a specialist edit is warranted the skill orchestrates it (skill-orchestrates, agent-executes) rather than doing isolated heavy work itself.
- Counter-dimension considered: the source-grounded analysis could suggest an isolated agent (context-window protection), but the analysis reads one card file against a spec that is already loaded, so isolation buys nothing and the approval gate wins — skill.
When this skill activates
Use this skill when an existing custom Lovelace card or panel needs its size declaration determined or corrected: it renders wrong in one view type or mode, its edit-mode overlays sit inside the content, it clips or leaves dead space, it reflows badly on tablet/mobile, or it simply lacks a considered getGridOptions() / getCardSize(). The skill determines the correct declaration and hands it to an implementation step that patches both callbacks in the target card file.
When NOT to activate
- greenfield card scaffolding (new card file, full lifecycle) →
ha-lovelace-card-scaffold - orchestrating a whole frontend solution across the card family →
ha-lovelace-solution - panels, panel-mode views, custom views, or panel UX →
ha-panel-add/ha-panel-author/ha-panel-ux-audit - adding a feature control row to a card →
ha-card-features-add - the card lifecycle / rendering framework or the full layout-antipattern catalogue →
ha/lovelace-card-patterns/ha/lovelace-layout-antipatterns - deploying or runtime-verifying on a live HA instance →
ha-integration-deployer/ha-integration-verifier
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 · 123 lines · 222 tokens per session scan A 10d4cdc61247
ha-card-sizing-determine is a skill published in the GitHub repository nolte/claude-home-assistant (1 stars, last pushed 1mo ago), licensed MIT. It adds 222 tokens to every session and 2,583 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.