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/esp-pio-handling/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/esp-pio-handling)<a href="https://agentmods.dev/skills/sensorsiot/embedded-ai-harness/esp-pio-handling"><img src="https://agentmods.dev/badge/skills/sensorsiot/embedded-ai-harness/esp-pio-handling/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/esp-pio-handling"><img src="https://agentmods.dev/badge/skills/sensorsiot/embedded-ai-harness/esp-pio-handling.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 121 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.00101 | $0.01283 |
| Opus 5 | $0.00051 | $0.00642 |
| Sonnet 5 | $0.00020 | $0.00257 |
| Haiku 4.5 | $0.00010 | $0.00128 |
Grade B, and why
esp-pio-handling 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.
| Permission denied | `sudo usermod -a -G dialout $USER`, then re-login | Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST $TESTBENCH_URL/api/flash \ How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PlatformIO Handling
Build, upload and monitor a PlatformIO ESP32 project, locally or through the testbench.
The testbench does not care which build system produced the image. Slot
discovery, /api/flash, GPIO download mode, crash-loop and flapping recovery are
the same either way and live in
esp-idf-handling. This skill covers only what
PlatformIO does differently. When something goes wrong with the bench rather
than the build, read that skill.
Step 1: Detect environment
Same as esp-idf-handling: if /api/info
answers, use the testbench; if nothing answers, flash over local USB. The
discovery script is shared —
.claude/skills/esp-idf-handling/discover-testbench.py --hosts.
Step 2: Build
pio run # default environment
pio run -e esp32dev # one environment
pio run -t clean
With several environments in platformio.ini, ask which to build rather than
guessing — they often target different boards. After a build, read the size
report, and check lib_deps when a header is missing rather than installing
libraries globally.
Step 3a: Upload — local USB
pio device list
pio run -t upload
pio run -e esp32dev -t upload
pio run -t upload && pio device monitor
Step 3b: Upload — testbench
Prefer POST /api/flash over driving esptool through RFC2217, for the reasons in
esp-idf-handling. What differs here is where the
images are and which ones exist.
PlatformIO writes them to .pio/build/<env>/, and there is no flash_args,
so use the explicit bin@<offset> form:
cd .pio/build/<env>
curl -s -X POST $TESTBENCH_URL/api/flash \
-F slot=SLOT1 -F chip=esp32 \
-F 'bin@[email protected]' \
-F 'bin@[email protected]' \
-F 'bin@[email protected]' | jq .
An Arduino-framework build also needs boot_app0.bin at 0xe000. It is not
in .pio/build/ — it ships inside the framework package, under
~/.platformio/packages/framework-arduinoespressif32*/tools/partitions/. Without
it the bootloader has no OTA-selection data and boots the wrong slot after an
update. An ESP-IDF project has no equivalent, which is why this step is not
simply a pointer.
What ships with it
1 file 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.
- 12d ago First seen · 126 lines · 101 tokens per session scan B 27c98a75cb1d
esp-pio-handling is a skill published in the GitHub repository SensorsIot/Embedded-AI-Harness (174 stars, last pushed 1mo ago), licensed MIT. It adds 101 tokens to every session and 1,283 once invoked, about $0.0005 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
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…
m5stack-core2
Hardware reference and development helper for the M5Stack Core2 family — a 2.0" touchscreen ESP32 (classic, Xtensa LX6) Controller built around an AXP192 power management IC, ILI9342C display, FT6336U capacitive touch, BM8563 RTC, and (on original/1.1/1.3 revisions) an MPU6886 or BMI270 IMU. Covers the plain Core2…
esp32-c6
Chip-level ESP-IDF capability reference for the ESP32-C6 SoC (single-core RISC-V HP core + RISC-V LP core, WiFi 6 + BLE 5.3 + Thread/Zigbee) — what the chip can do, distinct from any board's wiring. Use when a user wants to exploit ESP32-C6 hardware — WiFi 6/BLE/802.15.4 radio coexistence (Thread Border Router, Zigbee…
esp32-p4
Chip-level ESP-IDF capability reference for the ESP32-P4 SoC (dual-core RISC-V HP cores + a RISC-V LP core) — what the chip can do, distinct from any board's wiring. Use when a user wants to exploit ESP32-P4 hardware — MIPI-CSI/DSI with the on-chip ISP, hardware JPEG encode/decode, hardware H.264 encode, PPA/2D-DMA…