Borrowing it
Nothing to install: this file belongs to SensorsIot/Embedded-AI-Harness. 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/SensorsIot/Embedded-AI-Harness/main/.claude/skills/testbench-mqtt/SKILL.mdgit clone --depth 1 https://github.com/SensorsIot/Embedded-AI-HarnessWrote 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/sensorsiot/embedded-ai-harness/testbench-mqtt)<a href="https://agentmods.dev/skills/sensorsiot/embedded-ai-harness/testbench-mqtt"><img src="https://agentmods.dev/badge/skills/sensorsiot/embedded-ai-harness/testbench-mqtt/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/sensorsiot/embedded-ai-harness/testbench-mqtt"><img src="https://agentmods.dev/badge/skills/sensorsiot/embedded-ai-harness/testbench-mqtt.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Privilege Escalation · line 17 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
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.00120 | $0.01730 |
| Opus 5 | $0.00060 | $0.00865 |
| Sonnet 5 | $0.00024 | $0.00346 |
| Haiku 4.5 | $0.00012 | $0.00173 |
Grade B, and why
testbench-mqtt scanned grade B with 2 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 12d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
export TESTBENCH_URL=$(sudo python3 .claude/skills/esp-idf-handling/discover-testbench.py \ Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "$TESTBENCH_URL/api/info" # confirm before anything else How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ESP32 MQTT Broker
Base URL: $TESTBENCH_URL — see Step 0
Step 0: Point at a bench
There are several benches and their addresses move, so nothing here writes one
down. $BENCH is not usable either — a container cannot resolve mDNS.
Discover the bench and export its URL:
export TESTBENCH_URL=$(sudo python3 .claude/skills/esp-idf-handling/discover-testbench.py \
--url --name <bench-hostname>)
curl -s "$TESTBENCH_URL/api/info" # confirm before anything else
--url refuses to guess when more than one bench answers, so --name is
required whenever a second bench is powered on. TESTBENCH_URL is the same
variable pytest --wt-url falls back to.
The testbench can run an MQTT broker (mosquitto) for testing ESP32 devices that use MQTT for communication. The broker is accessible to devices connected to the testbench's WiFi AP.
Endpoints
Request and response shapes: FSD Appendix D.12.
Examples
# Start the MQTT broker
curl -X POST $TESTBENCH_URL/api/mqtt/start
# Check broker status
curl $TESTBENCH_URL/api/mqtt/status
# Stop the MQTT broker
curl -X POST $TESTBENCH_URL/api/mqtt/stop
MQTT Broker Details
| Property | Value |
|---|---|
| Broker | the bench address (from the LAN) or 192.168.4.1 (from the testbench AP) |
| Default port | 1883 |
| Authentication | None (open broker for testing) |
Common Workflows
-
Test ESP32 MQTT client:
- Ensure device is on testbench WiFi (see testbench-wifi)
POST /api/mqtt/start— start broker- Device connects to
192.168.4.1:1883 - Monitor device behavior via serial or UDP logs (see testbench-logging)
POST /api/mqtt/stop— stop broker when done
-
Test MQTT disconnect/reconnect:
- Start broker, let device connect
POST /api/mqtt/stop— device loses MQTT- Monitor device's reconnection behavior
POST /api/mqtt/start— device should reconnect
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.
- 12d ago First seen · 143 lines · 120 tokens per session scan B 17e6d7aaa3b7
testbench-mqtt is a skill published in the GitHub repository SensorsIot/Embedded-AI-Harness (174 stars, last pushed 1mo ago), licensed MIT. It adds 120 tokens to every session and 1,730 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
ea-skill
An AI-assisted workflow for developing and testing embedded-device software. Embedded software runs on hardware such as microcontrollers, and the workflow covers project setup, feature work, tests, device programming, debugging, verification, and records.
m5stack-cap-lora-1262
Hardware reference and firmware helper for the M5Stack Cap LoRa-1262 (SKU U214) — a snap-on cap for the Cardputer Adv (K132-Adv) and CardputerZero that carries a Semtech SX1262 sub-GHz LoRa radio (868–923 MHz, +22 dBm TX, external RP-SMA antenna) and an ATGM336H-6N GNSS receiver (GPS/QZSS/BeiDou/Galileo/GLONASS, UART…
new-device-skill
Build or update an M5Stack hardware skill in this marketplace — a Controller (a board that runs firmware, like Core2 or AtomS3), a Unit (a peripheral you drive from a Controller, like a ToF sensor or a relay), or a Chip (an Espressif SoC capability layer, like esp32-c6). Use whenever adding a new board/unit/chip to…
m5stack-tab5
Hardware reference and development helper for the M5Stack Tab5 (product code C145) — an ESP32-P4-based 5" touchscreen IoT/industrial terminal with an ESP32-C6 wireless co-processor, MIPI-DSI display, MIPI-CSI camera, ES8388 audio codec, BMI270 IMU, RX8130CE RTC, RS485, and a removable NP-F550 battery. Use this skill…
embedded-verification
Use after implementation complete - runs build-flash-monitor loop, verifies runtime behavior, no completion claims without fresh evidence.
embedded-testing-patterns
Embedded C test patterns using Unity, CMock, Ceedling, and QEMU.