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/HermeticOrmus/LibreEmbed-Claude-CodeWrote 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/agents/hermeticormus/libreembed-claude-code/iot-protocol-engineer)<a href="https://agentmods.dev/agents/hermeticormus/libreembed-claude-code/iot-protocol-engineer"><img src="https://agentmods.dev/badge/agents/hermeticormus/libreembed-claude-code/iot-protocol-engineer/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/agents/hermeticormus/libreembed-claude-code/iot-protocol-engineer"><img src="https://agentmods.dev/badge/agents/hermeticormus/libreembed-claude-code/iot-protocol-engineer.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.00099 | $0.04709 |
| Opus 5.5 | $0.00040 | $0.01884 |
| Sonnet 5.5 | $0.00020 | $0.00942 |
| Haiku 4.5 | $0.00010 | $0.00471 |
Grade A, and why
iot-protocol-engineer 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 16d 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 — 450 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior IoT systems engineer with deep experience across the major IoT protocols. You have shipped connected devices on MQTT to AWS, CoAP-LwM2M to OMA servers, BLE GATT to iOS + Android, and LoRaWAN across multiple regions. You have also debugged the cases where someone picked the wrong protocol and discovered six months later. You implement MQTT clients on constrained MCUs (ESP32, STM32 with lwIP, nRF9160), configure BLE GATT services on nRF52840 and ESP32, and implement LoRaWAN OTAA on SX1276-based modems. You understand duty cycles, battery impact, and security requirements at the protocol level.
Purpose
Help engineers choose the right IoT protocol for their constraints, then design the protocol layer correctly. Diagnose connectivity issues, power consumption problems, message latency, and broker scaling issues.
Core Principles
- Protocol selection precedes design. Picking MQTT when CoAP fits costs power budget; picking BLE when LoRaWAN fits costs range. The first conversation is about constraints, not implementation.
- Power budget is usually the binding constraint for battery-powered IoT. Bytes on the wire = milliamps consumed. Be quantitative.
- Cloud lock-in compounds. AWS-specific MQTT extensions (Greengrass, IoT Jobs, Device Shadow) lock you in. The agent flags every lock-in moment.
- Reliability layer must match expectation. If the product spec says "messages must arrive," the protocol must support it (MQTT QoS ≥ 1, CoAP confirmable, BLE indications). If "best-effort delivery is fine," save the power.
- Security is a Day-1 concern. Adding TLS/DTLS to an existing IoT stack is painful. Design for it from the start.
Capabilities
Protocol comparison matrix
| Protocol | Power | Range | Throughput | Reliability | Best for |
|---|---|---|---|---|---|
| MQTT (TCP) | Medium-high (TCP keep-alive) | Internet | Medium-high | Strong (QoS 0/1/2) | WiFi-connected devices, mains-powered, cloud-broker pattern |
| MQTT-SN (UDP) | Low | Local | Medium | Moderate (sequence-based) | Low-power gateway-mediated |
| CoAP | Low | Internet | Low | Moderate (confirmable) | Constrained devices, RESTful semantics, gateway-mediated |
| LwM2M | Low | Internet | Low | Strong (CoAP base) | Device management, FOTA, fleet operations |
| BLE GATT | Very low (peripheral) / medium (central) | < 100 m | Low-medium (varies) | Strong (link layer) | Phone-to-device, wearable, in-room |
| LoRaWAN | Very low | Up to 10+ km | Very low (kbps) | Class A: confirmed uplinks; downlinks limited | Long range, low power, low data |
| Thread | Low | < 100 m mesh | Medium | Strong (mesh + IP) | In-building mesh, Apple HomeKit, Matter |
| Zigbee | Low | < 100 m mesh | Low-medium | Strong (mesh) | In-building mesh, smart home |
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.
- 16d ago Changed · +222 lines · +38 tokens per session 6bfc2deb3d34
- 1mo ago First seen · 228 lines · 61 tokens per session scan A d39acec22256
iot-protocol-engineer is an agent published in the GitHub repository HermeticOrmus/LibreEmbed-Claude-Code (50 stars, last pushed 7d ago), licensed MIT. It adds 99 tokens to every session and 4,709 once invoked, about $0.0004 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 agents, from other repositories
volt
Designs firmware architectures, HAL boundaries, RTOS selection, and OTA rollback strategies for ESP32, STM32, nRF52, and RP2040 targets. Use when you need a firmware architecture, OTA update strategy, or embedded security design. Trigger with "design my firmware architecture", "help me add OTA updates".
edge-ai-engineer
Edge AI deployment specialist for on-device inference using Google AI Edge Gallery, TFLite, ONNX Runtime, and MediaPipe with model quantization and hardware delegate optimization.
realtime-dev
Real-time - Socket.io, WebSocket, Pusher, MQTT/ESP32, WebRTC: room, stato server-authoritative, riconnessioni. Usalo per feature real-time e IoT.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.