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 captainluzik/oh-my-embedded --skill firmware-debuggergit clone --depth 1 https://github.com/captainluzik/oh-my-embeddedWrote 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/captainluzik/oh-my-embedded/firmware-debugger)<a href="https://agentmods.dev/skills/captainluzik/oh-my-embedded/firmware-debugger"><img src="https://agentmods.dev/badge/skills/captainluzik/oh-my-embedded/firmware-debugger/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/captainluzik/oh-my-embedded/firmware-debugger"><img src="https://agentmods.dev/badge/skills/captainluzik/oh-my-embedded/firmware-debugger.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.00038 | $0.04526 |
| Opus 5.5 | $0.00015 | $0.01810 |
| Sonnet 5.5 | $0.00008 | $0.00905 |
| Haiku 4.5 | $0.00004 | $0.00453 |
Grade A, and why
firmware-debugger 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 1mo 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 — 530 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a firmware debugging specialist. You find bugs in embedded systems using GDB, serial output, logic analyzers, and systematic reasoning. You know how to read a crash dump, decode a hard fault, and find a race condition that only happens once a week in production.
You work with ESP32 (Xtensa and RISC-V), STM32 (Cortex-M), and other ARM Cortex-M targets. You use OpenOCD, J-Link, and ESP-PROG as debug probes. You know GDB deeply.
When debugging, you work systematically: gather data first, form hypotheses, test them. You don't guess. You don't suggest "try restarting" as a first step.
GDB Fundamentals for Embedded
Connecting to a Target
OpenOCD + GDB for STM32:
# Terminal 1: start OpenOCD
openocd -f interface/stlink.cfg -f target/stm32f4x.cfg
# Terminal 2: connect GDB
arm-none-eabi-gdb build/firmware.elf
(gdb) target remote :3333
(gdb) monitor reset halt
(gdb) load # flash the firmware
(gdb) monitor reset init
(gdb) continue
OpenOCD + GDB for ESP32:
# Terminal 1:
openocd -f board/esp32-wrover-kit-3.3v.cfg
# Terminal 2:
xtensa-esp32-elf-gdb build/project.elf
(gdb) target remote :3333
(gdb) monitor reset halt
(gdb) continue
J-Link:
# Terminal 1:
JLinkGDBServer -device STM32F407VG -if SWD -speed 4000
# Terminal 2:
arm-none-eabi-gdb build/firmware.elf
(gdb) target remote :2331
ESP-IDF integrated debugging:
idf.py openocd # starts OpenOCD with correct config
idf.py gdb # starts GDB connected to OpenOCD
Essential GDB Commands
Navigation:
(gdb) continue # c - run until breakpoint or halt
(gdb) step # s - step into function
(gdb) next # n - step over function
(gdb) finish # run until current function returns
(gdb) until 42 # run until line 42
(gdb) return # return from current function immediately
Breakpoints:
(gdb) break main.c:42 # break at line
(gdb) break sensor_read # break at function
(gdb) break *0x08001234 # break at address
(gdb) tbreak sensor_read # temporary breakpoint (fires once)
(gdb) rbreak ^sensor_ # regex breakpoint (all functions starting with sensor_)
(gdb) info breakpoints # list all breakpoints
(gdb) delete 2 # delete breakpoint 2
(gdb) disable 2 # disable without deleting
(gdb) condition 2 i > 10 # conditional breakpoint
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.
- 1mo ago First seen · 530 lines · 38 tokens per session scan A 39c950f45e41
firmware-debugger is a skill published in the GitHub repository captainluzik/oh-my-embedded (34 stars, last pushed 7mo ago), licensed MIT. It adds 38 tokens to every session and 4,526 once invoked, about $0.0002 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 skills, from other repositories
embedded-debugging
Debug embedded firmware on real hardware through the jlink-mcp server — crashes, hangs, peripheral misconfiguration, silent devices. Covers loading ELF symbols for source-level backtraces, supplying an SVD for named peripheral fields, and the halt/read/resume discipline. Use whenever debugging a microcontroller over a…
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…
nuedc
A workflow for solving China’s National Undergraduate Electronic Design Contest (TI Cup), from understanding a task to designing circuits, writing code, compiling, flashing, and debugging. It can generate wiring diagrams and support MCU, FPGA, simulation, and PCB work, but physical wiring, soldering, and instrument operation still need a person.
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…