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 skills/hermeticormus/libreembed-claude-code/iot-protocol-patternsnpx skills add HermeticOrmus/LibreEmbed-Claude-Code --skill iot-protocol-patternsgit clone --depth 1 https://github.com/HermeticOrmus/LibreEmbed-Claude-CodeWhat 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.00000 | $0.01624 |
| Opus 5 | $0.00000 | $0.00812 |
| Sonnet 5 | $0.00000 | $0.00325 |
| Haiku 4.5 | $0.00000 | $0.00162 |
Grade A, and why
iot-protocol-patterns 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 3d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iot-protocol-patterns
Knowledge Base
IoT protocol patterns for constrained MCUs and embedded Linux.
Pattern 1: MQTT Topic Structure
Well-structured topic hierarchy enables flexible filtering and routing:
device/{device_id}/telemetry ← sensor data (QoS 0, no retain)
device/{device_id}/status ← online/offline (QoS 1, retained)
device/{device_id}/cmd ← commands to device (QoS 1)
device/{device_id}/cmd/ack ← command acknowledgment
device/{device_id}/ota/cmd ← OTA start/control
device/{device_id}/ota/data ← firmware chunks
fleet/+/telemetry ← subscribe to all device telemetry
LWT (Last Will and Testament) configuration:
esp_mqtt_client_config_t cfg = {
.session.last_will = {
.topic = "device/" DEVICE_ID "/status",
.msg = "{\"online\":false}",
.qos = 1,
.retain = true, /* Retained: new subscribers see last status immediately */
},
};
On connect, publish: device/{id}/status = {"online":true} retained.
Pattern 2: Paho MQTT C Client (Linux/RTOS)
#include "MQTTClient.h"
#define BROKER_URI "ssl://broker.example.com:8883"
#define DEVICE_ID "device-001"
#define KEEPALIVE_SEC 60
static MQTTClient s_client;
static MQTTClient_connectOptions s_conn_opts = MQTTClient_connectOptions_initializer;
void mqtt_message_arrived(void *ctx, char *topic, int topic_len,
MQTTClient_message *msg)
{
/* Process command from broker */
handle_command(topic, msg->payload, msg->payloadlen);
MQTTClient_freeMessage(&msg);
MQTTClient_free(topic);
}
int mqtt_init(void)
{
MQTTClient_create(&s_client, BROKER_URI, DEVICE_ID,
MQTTCLIENT_PERSISTENCE_NONE, NULL);
s_conn_opts.keepAliveInterval = KEEPALIVE_SEC;
s_conn_opts.cleansession = 1;
s_conn_opts.username = "devices";
s_conn_opts.password = "secret";
MQTTClient_SSLOptions ssl = MQTTClient_SSLOptions_initializer;
ssl.trustStore = "/etc/ssl/mqtt-ca.pem";
s_conn_opts.ssl = &ssl;
MQTTClient_setCallbacks(s_client, NULL, NULL, mqtt_message_arrived, NULL);
int rc = MQTTClient_connect(s_client, &s_conn_opts);
if (rc != MQTTCLIENT_SUCCESS) { return rc; }
MQTTClient_subscribe(s_client, "device/" DEVICE_ID "/cmd", 1);
return 0;
}
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.
- 3d ago First seen · 195 lines · 0 tokens per session scan A aa38d8900d85
iot-protocol-patterns is a skill published in the GitHub repository HermeticOrmus/LibreEmbed-Claude-Code (44 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,624 tokens. 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 skills, from other repositories
hardware-iot-bus
Low-level I2C and SPI bus peripheral control for embedded Linux boards (Orange Pi, Raspberry Pi, RISC-V).
aether-iot-query
Use this skill when the user asks about a live AetherEdge runtime: channels, points, real-time values, history, alarms, rules, models, instances, routing, SHM health, service health, or system status. Use aether CLI commands to answer — do NOT inspect source code, local database files, or config YAMLs to answer…
aether-iot
Build, integrate, diagnose, or generate applications for the AetherEdge AI-native edge kernel. Use for AetherEdge onboarding, SDK compositions, device and topology clients, read-only operations UIs, MCP integration, Domain Packs, or governed IoT commands where live-state authority and physical-device safety must be…
avr-bare-metal-embedded
Curated Knowledge API for AI Agents — 68 MCP tools, 200+ skill packs, 46K chunks, semantic search over 670K vectors, 5-layer validation pipeline. Works with Claude Code, Cursor, Cline, Windsurf.
smart-product-dev
End-to-end IoT product development orchestration for TuyaOpen projects. Guides from requirements gathering → Tuya Platform product/DP creation → complete embedded firmware generation. State-machine: detects project state and picks up from wherever development currently stands.
edge-iot
Edge computing, IoT protocols, and embedded systems integration.