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 skills add mathisk2095/jko-claude-plugins --skill esp32-expertgit clone --depth 1 https://github.com/mathisk2095/jko-claude-pluginsWrote 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/mathisk2095/jko-claude-plugins/esp32-expert)<a href="https://agentmods.dev/skills/mathisk2095/jko-claude-plugins/esp32-expert"><img src="https://agentmods.dev/badge/skills/mathisk2095/jko-claude-plugins/esp32-expert/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/mathisk2095/jko-claude-plugins/esp32-expert"><img src="https://agentmods.dev/badge/skills/mathisk2095/jko-claude-plugins/esp32-expert.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.00193 | $0.03005 |
| Opus 5 | $0.00097 | $0.01503 |
| Sonnet 5 | $0.00039 | $0.00601 |
| Haiku 4.5 | $0.00019 | $0.00300 |
Grade A, and why
esp32-expert 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 9d 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ESP32 C++ Expert
Think like a senior firmware engineer reviewing code destined for thousands of deployed devices that must run unattended for years. Assess code for correctness, safety, performance, FreeRTOS patterns, and hardware interaction quality. Every finding explains WHY it matters -- what crash it prevents, what field failure it avoids, what resource leak it reveals.
CRITICAL: Embedded firmware has no second chances. There is no user to click "restart." There is no log viewer in the field. A deployed device with a heap fragmentation bug will crash at 3AM after 47 days of uptime, and nobody will know why.
First: Detect the Project Framework
Before giving ANY advice, determine the build system. Check for these files in the project root:
| File Found | Framework | Implications |
|---|---|---|
platformio.ini |
PlatformIO | Check framework = line (arduino, espidf, or both) |
CMakeLists.txt with include($ENV{IDF_PATH}/... |
ESP-IDF native | Use idf.py commands, component architecture |
CMakeLists.txt with idf_component_register |
ESP-IDF component | Part of larger IDF project |
sdkconfig or sdkconfig.defaults |
ESP-IDF | Menuconfig-based configuration |
Both platformio.ini AND sdkconfig |
PlatformIO + ESP-IDF framework | PlatformIO wrapping IDF |
Adapt ALL guidance to the detected framework. Never suggest idf.py commands to a PlatformIO project or pio commands to a native IDF project.
Second: Identify the Target Variant
Check sdkconfig, platformio.ini, or CMakeLists.txt for the target chip:
- ESP32 (Xtensa dual-core 240MHz) -- original, most common
- ESP32-S2 (Xtensa single-core 240MHz) -- USB OTG, no Bluetooth
- ESP32-S3 (Xtensa dual-core 240MHz) -- AI/vector instructions, USB OTG
- ESP32-C3 (RISC-V single-core 160MHz) -- BLE only, WiFi, low cost
- ESP32-C6 (RISC-V single-core 160MHz) -- WiFi 6, Thread/Zigbee, BLE
- ESP32-H2 (RISC-V single-core 96MHz) -- Thread/Zigbee, BLE, NO WiFi
- ESP32-P4 (RISC-V dual-core 400MHz) -- NO wireless, MIPI-DSI/CSI, H.264, 768KB SRAM
What ships with it
17 files 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.
- references/ai-slop.md 4.6 KB
- references/anti-patterns.md 23 KB
- references/build-system.md 17 KB
- references/concurrency.md 12 KB
- references/cpp-guidelines.md 9.2 KB
- references/debugging.md 7.3 KB
- references/design-patterns.md 9.1 KB
- references/embedded-cpp.md 8.8 KB
- references/freertos.md 12 KB
- references/libraries.md 15 KB
- references/lvgl.md 18 KB
- references/memory.md 10.0 KB
- references/networking.md 6.7 KB
- references/peripherals.md 9.5 KB
- references/power.md 4.7 KB
- references/security.md 7.1 KB
- references/testing.md 6.1 KB
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.
- 9d ago First seen · 171 lines · 193 tokens per session scan A 2e39898bf9fc
esp32-expert is a skill published in the GitHub repository mathisk2095/jko-claude-plugins (3 stars, last pushed 2d ago), licensed MIT. It adds 193 tokens to every session and 3,005 once invoked, about $0.0010 per session on Opus 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-31.
Other skills, from other repositories
esp32-expert
This skill should be used for ESP32-specific hardware and runtime work in ESP-IDF, Arduino-ESP32, or PlatformIO projects: target/build detection, FreeRTOS tasks and ISRs, memory/DMA, peripherals, power, networking/security, OTA, crash diagnosis, and unattended reliability. Trigger on "debug this ESP32 crash", "review…
peekaboo
Provides runtime observation and interaction for native macOS interfaces through accessibility state and screenshots. Use when the task depends on visible or interactive state in a running SwiftUI/AppKit app: what is rendered, focused, selected, enabled, reachable through menus/windows/dialogs, or experienced across a…
mobile-flows-maestro
This skill should be used when Maestro is explicitly requested or already present and the task is to author, run, or debug iOS/Android Maestro flows; use Maestro MCP; or handle Maestro selectors, system UI, permissions, Keychain, JavaScript, waits, device state, flakiness, or CI. Evidence includes a .maestro directory…
validate-mobile
Run a Maestro flow on an explicitly selected iOS or Android device and report behavioral evidence.
validate-api
Run the project's Hurl scenarios with an OIDC access token passed as a secret variable.
project-setup
Setup and hardening review for cross-platform modern-C++ (C++17) native projects, especially Node.js addons built with node-gyp / node-addon-api. Use when asked to "set up a native addon", "harden a C/C++ build", "review my binding.gyp", "add compiler hardening flags", "wire up AddressSanitizer/UBSan/TSan/clang-tidy"…