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 agentmods add commands/nodnarbnitram/claude-code-extensions/ha-automation-lintgit clone --depth 1 https://github.com/nodnarbnitram/claude-code-extensionsWrote 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/commands/nodnarbnitram/claude-code-extensions/ha-automation-lint)<a href="https://agentmods.dev/commands/nodnarbnitram/claude-code-extensions/ha-automation-lint"><img src="https://agentmods.dev/badge/commands/nodnarbnitram/claude-code-extensions/ha-automation-lint.svg" alt="Measured on agentmods" 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 | $0.00011 | $0.00715 |
| Opus 5 | $0.00005 | $0.00358 |
| Sonnet 5 | $0.00002 | $0.00143 |
| Haiku 4.5 | $0.00001 | $0.00072 |
Grade A, and why
ha-automation-lint 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 5d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Home Assistant Automation Linter
Validate Home Assistant automation YAML configuration files for syntax errors, deprecated patterns, and best practices.
Task
-
Identify the target file(s):
- If
$1is provided, validate that specific automation file - If no argument, search for automation files in current directory (*.yaml, *.yml in automations/ or config/)
- Handle both single automation files and automation.yaml with multiple entries
- If
-
Validate YAML syntax:
- Check for valid YAML structure using
yamllintor Python yaml parser - Report any syntax errors with line numbers
- Ensure proper indentation and key structure
- Check for valid YAML structure using
-
Check Home Assistant automation structure:
- Verify required fields:
alias,trigger,condition(optional),action - Validate trigger types:
state,numeric_state,time,time_pattern,sun,event,mqtt,webhook,device,zone,geo_location,tag,calendar,persistent_notification,template - Validate condition types:
state,numeric_state,time,sun,zone,template,and,or,not - Validate action structure and common services
- Check automation mode:
single,restart,queued,parallel(with optionalmaxforqueued/parallel)
- Verify required fields:
-
Detect deprecated patterns:
- Old condition shortcut syntax (should use full object structure)
- Deprecated
platform:syntax in triggers (should betrigger:) - Missing explicit
conditions:array when multiple conditions exist - Using
if:instead of structured conditions - Deprecated service call formats (e.g., old entity_id vs target syntax)
-
Suggest best practices:
- Recommend using
chooseaction instead of multiple sequential automations with same trigger - Suggest template conditions instead of complex state conditions
- Recommend using device triggers for cleaner configuration
- Suggest naming conventions: descriptive aliases, kebab-case for templates
- Point out performance improvements (e.g., using numeric_state triggers instead of template for numeric comparisons)
- Flag potential issues: empty conditions/actions, missing delay units, hardcoded values that should be templated
- Recommend using
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.
- 5d ago First seen · 63 lines · 11 tokens per session scan A b5cb4ab03648
ha-automation-lint is a command published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 715 once invoked, about $0.0001 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.