embedded-debug-entry

embedded-debug-entry is a skill for Claude Code, Codex from easyzoom/aix-skills. It costs 37 tokens per session (1,312 once invoked), scanned A, original, MIT.

A starting guide for diagnosing embedded devices such as microcontrollers, firmware, development boards, and real-time operating systems.

In plain words
What is it for?
Use it when a device cannot connect, be flashed, boot, produce logs, communicate with peripherals, or handle bootloader, RTOS, or low-power issues.
Why use it?
It classifies the device, failure stage, connection method, and risk before choosing a more specific debugging approach.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when a device cannot connect, be flashed, boot, produce logs, communicate with peripherals, or handle bootloader, RTOS, or low-power issues.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/easyzoom/aix-skills/embedded-debug-entry
Install

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.

Any agent
npx skills add easyzoom/aix-skills --skill embedded-debug-entry
Clone the repo
git clone --depth 1 https://github.com/easyzoom/aix-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for embedded-debug-entry

README.md
[![agentmods](https://agentmods.dev/badge/skills/easyzoom/aix-skills/embedded-debug-entry/github.svg)](https://agentmods.dev/skills/easyzoom/aix-skills/embedded-debug-entry)
Your own site
<a href="https://agentmods.dev/skills/easyzoom/aix-skills/embedded-debug-entry"><img src="https://agentmods.dev/badge/skills/easyzoom/aix-skills/embedded-debug-entry/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.

agentmods 80×15 button for embedded-debug-entry

Your own site · 80×15
<a href="https://agentmods.dev/skills/easyzoom/aix-skills/embedded-debug-entry"><img src="https://agentmods.dev/badge/skills/easyzoom/aix-skills/embedded-debug-entry.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,312 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00037 $0.01312
Opus 5.5 $0.00015 $0.00525
Sonnet 5.5 $0.00007 $0.00262
Haiku 4.5 $0.00004 $0.00131

Measured 1mo ago against content hash 123ab2c77409, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

embedded-debug-entry 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.

skills/embedded-debug-entry/SKILL.md · 110 lines

How it starts

The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Embedded Debug Entry

Overview

Use this skill as the first stop for embedded debugging. The agent should classify the target, failure phase, access method, toolchain, and risk level, then route to the narrowest specialized skill instead of guessing from incomplete context.

When To Use

Use this skill when:

  • The user reports an embedded device, MCU, board, firmware, RTOS, bootloader, or peripheral issue.
  • The architecture or debugging path is unclear.
  • The task might involve flashing, serial logs, SWD/JTAG, UART, ADB, bootloaders, low power, or hardware signals.

Do not use this skill when the user already named a more specific skill path, such as Cortex-M HardFault, 8051 timer, RISC-V trap, or embedded Linux SSH login.

First Questions

Ask only what is needed to route:

  • Target type: MCU, embedded Linux device, mixed SoC, module, or unknown board.
  • Architecture or chip family: Cortex-M, Cortex-R, RISC-V, 8051, Linux-capable ARM, or unknown.
  • Failure phase: cannot connect, cannot flash, no boot, crash/fault, no logs, peripheral failure, RTOS issue, bootloader issue, low-power issue.
  • Available access: SWD/JTAG, serial UART, SSH, ADB, Telnet, local console, logic analyzer, oscilloscope, or vendor tool.
  • Toolchain and artifacts: ELF/HEX/MAP, firmware log, programmer output, schematic, boot log, or fault dump.

Routing Guide

Use the most specific path:

Symptom or target Prefer
Cortex-M MCU, SWD/JTAG, HardFault, startup cortex-m-debug
Cortex-R5/R4/R7, TCM, MPU, lockstep, safety core cortex-r5-debug
8051/51/STC/Nuvoton/Silabs C8051 8051-mcu-debug
RISC-V MCU, OpenOCD/GDB, trap, CSR riscv-mcu-debug
Embedded Linux login before debugging embedded-linux-login-debug
OpenOCD/J-Link/ST-Link probe, SWD/JTAG attach openocd-jlink-stlink-debug
Flash/download/verify/connect failure mcu-flashing-debug
UART boot log, serial console, 乱码, no logs embedded-serial-log-debug
Crash, exception, trap, fault, stack corruption embedded-fault-debug
GPIO/UART/SPI/I2C/PWM/ADC bring-up embedded-peripheral-bringup
Sensor driver, IMU, I2C/SPI sensor data sensor-driver-integration
QSPI/OSPI flash, XIP, memory-mapped boot qspi-xip-flash-debug
FreeRTOS kernel: tasks, heap, tick, ISR API freertos-kernel-debug
Zephyr devicetree, Kconfig, west, drivers zephyr-integration
RT-Thread BSP, FinSH, device framework, DFS rt-thread-integration
General RTOS scheduling, stacks, priorities rtos-debug
STM32 HAL/LL, CubeMX, clocks, DMA, NVIC stm32-hal-ll-integration
ESP-IDF, sdkconfig, partitions, NVS, Wi-Fi esp-idf-integration
Nordic nRF Connect SDK, BLE, DFU, Partition Mgr nrf-connect-sdk-integration
BLE GATT services, characteristics, MTU, pairing ble-gatt-integration
Bootloader, app jump, upgrade state bootloader-debug
MCUboot image slots, signing, swap, rollback mcuboot-integration
OTA package, transport, validation, activation ota-update-integration
Sleep, wakeup, current consumption, lost debug low-power-debug
Power, reset, clock, pins, board-level signals hardware-interface-debug

Read the full file on GitHub · 110 lines

Changes

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.

  1. 1mo ago First seen · 110 lines · 37 tokens per session scan A 123ab2c77409

Subscribe to this mod's changes

embedded-debug-entry is a skill published in the GitHub repository easyzoom/aix-skills (38 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 1,312 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

routeros-mac-telnet

MAC-Telnet protocol (MikroTik Layer-2 terminal/exec over UDP 20561) wire format, session handshake, and MD5 + MTWEI (EC-SRP) authentication. Use when: implementing or debugging a MAC-Telnet client/server, reaching a RouterOS device by MAC address without IP, parsing MAC-Telnet packets, understanding the WinBox-style…

tikoci/routeros-skills · 141 tokens

routeros-syntax-inspection

Inspecting and validating RouterOS command/script syntax against a live device via /console/inspect (highlight, completion, syntax, child) and :parse IL. Use when: validating RouterOS commands before execution, explaining or linting RouterOS scripts, building syntax-aware tooling (LSP servers, validators, agent…

tikoci/routeros-skills · 111 tokens

routeros-sniffer

RouterOS packet capture and TZSP streaming for protocol debugging. Use when: capturing packets on RouterOS, setting up /tool/sniffer, streaming live traffic via TZSP, using firewall mangle action=sniff-tzsp, debugging network protocols on MikroTik, receiving TZSP with Wireshark or tshark, saving pcap files from…

tikoci/routeros-skills · 107 tokens

tia-doctor

Manual, read-only prerequisite probe for TIA Portal V21 and its modular Openness API, with an optional Python TIA Scripting check.

Czarnak/totally-integrated-claude · 33 tokens

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…

Klievan/jlink-mcp · 77 tokens

container-home

Answer questions, assist with planning, and help with design decisions for Mick's off-grid shipping container lake home project. Trigger when the user mentions the container home, lake home, Stewart County, LBL, the expansion, solar system, septic permitting, or retirement property.

mickpletcher/AI-Skills · 57 tokens