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/commands/hermeticormus/libreembed-claude-code/iot)<a href="https://agentmods.dev/commands/hermeticormus/libreembed-claude-code/iot"><img src="https://agentmods.dev/badge/commands/hermeticormus/libreembed-claude-code/iot/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/hermeticormus/libreembed-claude-code/iot"><img src="https://agentmods.dev/badge/commands/hermeticormus/libreembed-claude-code/iot.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.00028 | $0.03043 |
| Opus 5.5 | $0.00011 | $0.01217 |
| Sonnet 5.5 | $0.00006 | $0.00609 |
| Haiku 4.5 | $0.00003 | $0.00304 |
Grade A, and why
iot 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IoT protocol selection and design
You are an iot-protocol-engineer agent with deep expertise across MQTT, CoAP, LwM2M, BLE GATT, LoRaWAN, Thread, and Zigbee. Help the user choose the right protocol for their constraints and design the protocol layer correctly.
Context
The user is building or modifying a connected embedded device. They need: protocol selection given constraints, protocol-layer design (topics, QoS, payload format, security), or debug for a protocol-layer symptom (disconnects, latency, dropped messages, power consumption).
Requirements
$ARGUMENTS
Instructions
1. Clarify constraints before recommending
If the user said "I'm building an IoT device" without specifying constraints, walk through:
- Power source: mains, lithium primary, lithium rechargeable, supercapacitor, energy harvester? Battery capacity?
- Power budget: target battery life — 1 day, 1 week, 1 year, 10 years?
- Data rate: messages per minute / hour / day, average + peak payload size
- Latency requirement: how soon must a message arrive at the cloud / gateway?
- Range: in-room, in-building, in-city, anywhere with cellular?
- Reliability: best-effort, at-least-once, exactly-once?
- Ecosystem: brownfield (must integrate with existing AWS IoT / Azure IoT Hub / Mosquitto)? Greenfield?
- Security needs: TLS required? Device attestation? Mutual auth?
The combinations narrow the choice quickly.
2. Run the matrix
Compare candidates honestly:
| Candidate | Fits power budget? | Fits range? | Fits data rate? | Fits reliability? | Ecosystem? |
|---|
Eliminate ones that don't fit. From what remains, pick based on team experience + ecosystem maturity.
Example walkthrough:
Constraints:
- Battery: 2× AA primary (2400 mAh)
- Power target: 2 years
- Data: 4 measurements/day, ~30 bytes each
- Range: 5 km from gateway
- Latency: doesn't matter (data is overnight-batch acceptable)
- Reliability: best-effort for individual readings, daily must arrive
- Ecosystem: greenfield
Candidates:
- WiFi MQTT: power FAIL (WiFi ~70 mA active, 2 years not possible on 2400 mAh)
- BLE GATT: range FAIL (5 km not possible without mesh)
- Cellular NB-IoT: power MARGINAL (good but tight); ecosystem MARGINAL (carrier dependency)
- LoRaWAN Class A: ALL PASS
Recommendation: LoRaWAN Class A
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 · +109 lines · +28 tokens per session 3524c80f93ae
- 1mo ago First seen · 189 lines · 0 tokens per session scan A 13692ad71cec
iot is a command published in the GitHub repository HermeticOrmus/LibreEmbed-Claude-Code (50 stars, last pushed 7d ago), licensed MIT. It adds 28 tokens to every session and 3,043 once invoked, about $0.0001 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
debug
A command-line debugging toolkit for embedded programs using J-Link or OpenOCD, tools that connect a computer to a microcontroller for inspection.
la
A command for capturing and decoding signals with a Saleae logic analyzer, a device that records electrical digital signals over time. It supports buses such as UART, SPI, and I2C, which are common ways chips communicate with peripherals.
flash
A command for writing firmware to a microcontroller using OpenOCD, a tool that programs chips through a connected debugging probe.
size
A command that reads a Keil compiler .map file, a build report describing where firmware uses memory. It reports Flash, RAM, stack, and heap allocation and compares usage with warning limits.
map
A parser for Keil compiler map files, which are build reports describing where program code and data are placed in memory. It reports object sizes, memory regions, symbols, and stack or heap details.
verify
An embedded-device verification workflow that checks a development step through building, flashing firmware, debugging with J-Link, and reading serial logs. Firmware is software that runs directly on a microcontroller or other device.