Borrowing it
Nothing to install: this file belongs to jacedomotz/domotz-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jacedomotz/domotz-mcp-server/main/.claude/skills/domotz-api/SKILL.mdgit clone --depth 1 https://github.com/jacedomotz/domotz-mcp-serverWrote 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/jacedomotz/domotz-mcp-server/domotz-api)<a href="https://agentmods.dev/skills/jacedomotz/domotz-mcp-server/domotz-api"><img src="https://agentmods.dev/badge/skills/jacedomotz/domotz-mcp-server/domotz-api/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/jacedomotz/domotz-mcp-server/domotz-api"><img src="https://agentmods.dev/badge/skills/jacedomotz/domotz-mcp-server/domotz-api.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.00052 | $0.03125 |
| Opus 5 | $0.00026 | $0.01563 |
| Sonnet 5 | $0.00010 | $0.00625 |
| Haiku 4.5 | $0.00005 | $0.00313 |
Grade A, and why
domotz-api 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domotz MCP Server - API Skill
Architecture
This MCP server consolidates 133 Domotz API actions into 10 category tools. Instead of 130+ flat tool definitions, each category tool uses an action parameter for routing to the correct endpoint.
How it works:
- Every tool call requires an
actionstring (e.g.,"list","get","status_history") - The generic dispatcher (
lib/registry.js) looks up the action in the category's action map - URL path parameters like
{agent_id}are replaced from your arguments - Query parameters, request bodies, and HTTP method are all derived from the action definition
Key insight: You never specify HTTP methods or URLs. Just pick the right tool, set the action, and provide the required parameters.
Quick Reference: The 10 Tools
| Tool | Actions | Description |
|---|---|---|
domotz_agents |
31 | Collectors: list, status, uptime, VPN, variables, topology |
domotz_devices |
17 | Devices: list, get, edit, status history, RTD, connect |
domotz_monitoring |
13 | SNMP/TCP sensors (Eyes): create, delete, history, triggers |
domotz_alerts |
8 | Alert profiles: list, bind/unbind to agents and devices |
domotz_network |
14 | Scan policies, interfaces, routed networks, excluded devices |
domotz_configuration |
8 | Config backups, credentials, SNMP authentication |
domotz_power |
7 | Power actions, outlets, attach/detach devices |
domotz_drivers |
8 | Custom drivers: associations, execute actions |
domotz_inventory |
19 | Custom fields, tags, device profiles, device types |
domotz_account |
5 | User info, API usage, areas, teams |
Common Parameters
These parameters appear across multiple tools:
| Parameter | Type | Used By | Description |
|---|---|---|---|
action |
string | All tools | Required. Selects which API operation to perform |
agent_id |
integer | Most tools | Domotz collector/agent ID |
device_id |
integer | Device-scoped tools | Device ID within a collector |
from |
string | Time-series actions | Start time (ISO 8601 or relative). Defaults to 1 week ago |
to |
string | Time-series actions | End time. Defaults to now |
page_size |
number | Paginated actions | Items per page (1-1000) |
page_number |
number | Paginated actions | Page index (0-based) |
body |
object | Create/update actions | JSON request body for POST/PUT operations |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 256 lines · 52 tokens per session scan A bfb48396fa76
domotz-api is a skill published in the GitHub repository jacedomotz/domotz-mcp-server (6 stars, last pushed 7mo ago), licensed MIT. It adds 52 tokens to every session and 3,125 once invoked, about $0.0003 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
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
doca-socket-relay
Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
hsb-flash
Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.