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.
git 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-integration-scaffold)<a href="https://agentmods.dev/commands/nodnarbnitram/claude-code-extensions/ha-integration-scaffold"><img src="https://agentmods.dev/badge/commands/nodnarbnitram/claude-code-extensions/ha-integration-scaffold/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/commands/nodnarbnitram/claude-code-extensions/ha-integration-scaffold"><img src="https://agentmods.dev/badge/commands/nodnarbnitram/claude-code-extensions/ha-integration-scaffold.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.00010 | $0.01904 |
| Opus 5.5 | $0.00004 | $0.00762 |
| Sonnet 5.5 | $0.00002 | $0.00381 |
| Haiku 4.5 | $0.00001 | $0.00190 |
Grade A, and why
ha-integration-scaffold 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 1mo 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Home Assistant Integration Scaffold
Generate boilerplate files for a new Home Assistant custom integration.
Arguments: $ARGUMENTS
Important:
- First argument: domain (kebab-case identifier, e.g.,
my-integration) - Optional flags:
--with-config-flow: Include config_flow.py for UI-based configuration--platforms: Comma-separated list of platforms (e.g.,sensor,switch,light)
Your Task
Follow these steps to scaffold the Home Assistant integration:
Step 1: Parse Arguments
Extract from $ARGUMENTS:
- Domain: The first argument (kebab-case identifier, e.g.,
my-integration) - Config Flow Flag: Check for
--with-config-flow(optional) - Platforms: Extract from
--platforms sensor,switch,...(optional)
Examples:
/ha-integration-scaffold my-device/ha-integration-scaffold weather-api --with-config-flow/ha-integration-scaffold smart-lights --platforms sensor,switch,light/ha-integration-scaffold iot-hub --with-config-flow --platforms sensor,binary_sensor
Step 2: Validate Domain
- Must be kebab-case (lowercase letters and hyphens only)
- Convert underscores to hyphens if needed
- Store as both kebab-case (domain) and snake_case (for Python module name)
- Domain:
my-integration - Python module:
my_integration
- Domain:
Step 3: Generate manifest.json
Create custom_components/<domain>/manifest.json with:
{
"domain": "domain-name",
"name": "Domain Name",
"codeowners": ["@username"],
"config_entries_only": true,
"documentation": "https://github.com/username/ha-domain-name",
"homeassistant": "2024.1.0",
"iot_class": "cloud_polling",
"issue_tracker": "https://github.com/username/ha-domain-name/issues",
"requirements": [],
"version": "1.0.0"
}
Key points:
domain: Use the kebab-case version (e.g.,my-integration)name: Title-case version (e.g.,My Integration)homeassistant: Set to a recent stable version (e.g.,2024.1.0)iot_class: Choose appropriate class:local_polling: Local network, pollingcloud_polling: Cloud API, pollinglocal_push: Local network, push updatescloud_push: Cloud API, push updates
config_entries_only: Set totrue(required for modern integrations)requirements: Empty array initially (add dependencies as needed)
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.
- 1mo ago First seen · 262 lines · 10 tokens per session scan A f0d811ee7d45
ha-integration-scaffold is a command published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 6mo ago), licensed MIT. It adds 10 tokens to every session and 1,904 once invoked, about $0.0000 per session on Opus 5.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
tapeout
Produce a complete, fab-ready export bundle for a routed board — or refuse loudly. Superset of the manufacturing-readiness skill: runs the three sign-off pre-gates, then adds a BOM part-number-resolution gate, a per-rule warning-review gate (assembly-affecting warnings block unless explicitly acknowledged), schematic…
eol-report
EOL/EOS risk report — devices, OS versions, and firmware approaching or past end-of-life/end-of-support, prioritized by criticality.
rvcsi-calibrate
Learn a v0 per-subcarrier baseline (mean amplitude) from a .rvcsi capture.
esp-harden
Harden and inspect ESP32 firmware for field failures, crashes, memory, and security.
pentest-wireless
You are an expert wireless security tester covering Wi-Fi, Bluetooth, and IoT radio protocols. For AUTHORIZED testing only.
device-info
A device-scanning command that identifies the connected chip and its VID:PID hardware identifiers. It also provides suggestions for the driver needed to use the device.