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 agentmods add skills/bahaabdelwahed/embedded-claude-plugin/boot-debug-confignpx skills add bahaabdelwahed/embedded-claude-plugin --skill boot-debug-configgit clone --depth 1 https://github.com/bahaabdelwahed/embedded-claude-pluginWrote 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/bahaabdelwahed/embedded-claude-plugin/boot-debug-config)<a href="https://agentmods.dev/skills/bahaabdelwahed/embedded-claude-plugin/boot-debug-config"><img src="https://agentmods.dev/badge/skills/bahaabdelwahed/embedded-claude-plugin/boot-debug-config.svg" alt="Measured on agentmods" 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.00106 | $0.01258 |
| Opus 5 | $0.00053 | $0.00629 |
| Sonnet 5 | $0.00021 | $0.00252 |
| Haiku 4.5 | $0.00011 | $0.00126 |
Grade A, and why
boot-debug-config 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 6d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Boot and Debug Configuration
Extract boot mode configuration and debug interface information from reference manual and programming manual PDFs.
What to Extract
Boot Modes
- Boot mode selection mechanism (BOOT0/BOOT1 pins or option bytes nBOOT0/nBOOT1)
- Boot mode table: pin/option byte combinations and resulting boot source
- Boot addresses: Main Flash (0x08000000), System memory (bootloader), embedded SRAM
- Boot address remapping (if available on the family)
System Memory Bootloader
- Built-in bootloader location (System memory, factory-programmed by ST)
- Supported bootloader protocols: USART, I2C, SPI, USB DFU, CAN, FDCAN
- Which pins are used for each bootloader protocol
- Bootloader version and supported commands
Debug Interfaces
- SWD (Serial Wire Debug): SWDIO, SWCLK pins
- JTAG: TMS, TCK, TDI, TDO, TRST pins (if applicable)
- SWO (Serial Wire Output): trace pin for ITM/printf debugging
- Debug port pin locations (which GPIO port/pins)
Debug Configuration
- DBGMCU register: debug support during low-power modes
- Freeze peripherals during debug (timers, watchdogs, RTC)
Where to Find This Information
Reference Manual - Boot Configuration
Glob pattern: docs/reference-manual/*.pdf
- Read pages 1-5 (ToC)
- Find section titled "Boot configuration" or "System memory boot mode" (often in chapter 2 or a dedicated boot chapter)
- Extract the boot mode selection table (BOOT0/BOOT1 -> boot source)
- Find "SYSCFG" chapter for memory remap register if applicable
Reference Manual - Debug
- From ToC find the "Debug support (DBG)" chapter (usually near the end)
- Contains DBGMCU_IDCODE (device ID), DBGMCU_CR (debug configuration)
- Lists which peripherals can be frozen during debug halt
Programming Manual
Glob pattern: docs/programming-manual/*.pdf
- Cortex-M programming manual contains debug port architecture details
- Look for "Debug port" or "CoreSight" sections
- Contains DAP (Debug Access Port) architecture, breakpoint/watchpoint configuration
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.
- 6d ago First seen · 112 lines · 106 tokens per session scan A 213979bbddc0
boot-debug-config is a skill published in the GitHub repository bahaabdelwahed/embedded-claude-plugin (5 stars, last pushed 5mo ago), licensed MIT. It adds 106 tokens to every session and 1,258 once invoked, about $0.0005 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
gke-ai-troubleshooting-tpu-dynamic-slices-monitoring
Monitors, troubleshoots, and manages GKE TPU Dynamic Slices custom resources. Use when checking TPU slice lifecycle states, troubleshooting slice provisioning failures, validating single-slice or multi-slice (JobSet) workload manifests, or safely patching stuck finalizers and disabling the slice controller. Don't use…
gke-ai-troubleshooting-tpu-vbar-oom
Diagnoses and prevents vbarcontrolagent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbarcontrolagent crashes, memory cgroup OOMs in serial console…
competition-firmware-layout
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for firmware images, partition tables, boot chains, update packages, extracted filesystems, embedded configs, and device-facing trust boundaries. Use when the user asks to unpack firmware, map partition layout, inspect bootloader or init…
esp32-log-triage
Parse and classify ESP32 serial log output to identify FastLED-related errors, RMT/I2S/SPI driver faults, timing violations, RTOS issues, and crash signatures. Use when debugging unexpected device behavior, boot failures, or LED output problems on ESP32.
doca-flow
Build and debug DOCA Flow applications on supported NVIDIA NICs/DPUs: define match/action pipes, initialize ports and representors, choose forwarding targets, validate pipes before hardware programming, read counters, match the Flow version to the installed DOCA release, and diagnose Flow API errors. Trigger on DOCA…
memory-audit
Audit embedded code for stack overflow risks, heap fragmentation, static allocation patterns, and memory leaks. Use when investigating OOM crashes, optimizing memory usage, or reviewing memory-critical code on constrained devices.