What is sbl-debugger-mcp CLAUDE.md?

A set of Claude Code instructions for using an MCP server to debug ARM Cortex-M firmware. Firmware is the software running directly on an embedded device.

Connecting to a target, flashing firmware, checking device state, taking debugging snapshots, stepping through code, managing breakpoints, and inspecting registers, memory, and peripherals.

It gives the agent a guide to the debugger’s tools and common workflows, making hardware debugging actions easier to carry out consistently.

How soundbytelabs/sbl-debugger-mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to soundbytelabs/sbl-debugger-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/soundbytelabs/sbl-debugger-mcp/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/soundbytelabs/sbl-debugger-mcp

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/soundbytelabs/sbl-debugger-mcp/claude-md/github.svg)](https://agentmods.dev/instructions/soundbytelabs/sbl-debugger-mcp/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/soundbytelabs/sbl-debugger-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/soundbytelabs/sbl-debugger-mcp/claude-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/soundbytelabs/sbl-debugger-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/soundbytelabs/sbl-debugger-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,316 This file is loaded in full into every session.

When invoked 1,316 The same file — it is already loaded in full.

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.

Model	Per session	Once invoked
Fable 5.1	$0.01316	$0.01316
Opus 5.5	$0.00526	$0.00526
Sonnet 5.5	$0.00263	$0.00263
Haiku 4.5	$0.00132	$0.00132

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

Security

Grade A, and why

sbl-debugger-mcp CLAUDE.md 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 2mo 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.

CLAUDE.md · 107 lines

How it starts

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

sbl-debugger MCP Server — Agent Guide

ARM Cortex-M hardware debugger via GDB + OpenOCD. Attach to a target, flash firmware, set breakpoints, step through code, inspect registers/memory/peripherals.

Tool Overview

Tool	Purpose
`debug_attach`	Connect to target (starts OpenOCD + GDB)
`debug_detach`	Disconnect and clean up
`debug_sessions`	List active sessions
`debug_status`	Check target state (halted/running)
`debug_snapshot`	Complete state in one call — frame, registers, backtrace, locals, source
`load`	Flash ELF to target
`halt`	Stop execution (GDB interrupt, falls back to OpenOCD TCL)
`continue_execution`	Resume execution
`wait_for_halt`	Block until target stops (breakpoint, watchpoint, etc.)
`step` / `step_over` / `step_out` / `step_instruction`	Step through code
`run_to`	Run to a specific function/line/address
`reset`	Reset target (optionally halt after reset)
`breakpoint_set` / `breakpoint_delete` / `breakpoint_list`	Manage breakpoints
`watchpoint_set`	Hardware watchpoint on memory/variable
`read_registers` / `write_register`	CPU register access
`read_memory` / `write_memory`	Raw memory access
`read_locals`	Local variables in current frame
`print_expr`	Evaluate C/C++ expression (struct fields, array indexing, pointer deref)
`backtrace`	Call stack
`disassemble`	Disassemble at address or current PC
`list_peripherals` / `list_registers` / `read_peripheral_register` / `read_peripheral`	SVD-decoded peripheral inspection
`monitor`	Raw OpenOCD command (escape hatch)

Common Workflows

Basic Debug Session

debug_attach(target="daisy", elf="/path/to/firmware.elf")
load(name="daisy")                    # Flash firmware
continue_execution(name="daisy")      # Start running
halt(name="daisy")                    # Stop to inspect
debug_snapshot(name="daisy")          # See everything at once
continue_execution(name="daisy")      # Resume
debug_detach(name="daisy")            # Clean up

Read the full file on GitHub · 107 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.

2mo ago First seen · 107 lines · 1,316 tokens per session scan A 03440c192c9a

Subscribe to this mod's changes

sbl-debugger-mcp CLAUDE.md is an instructions file published in the GitHub repository soundbytelabs/sbl-debugger-mcp (0 stars, last pushed 8mo ago), licensed MIT. It adds 1,316 tokens to every session, about $0.0053 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-31.

Debugging Hardware and IoT

sbl-debugger-mcp CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
sbl-debugger-mcp CLAUDE.mdsoundbytelabs/sbl-debugger-mcp	Instructions file	0	8mo ago	MIT	A	1,316	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	2,022	GitHub Copilot

sbl-debugger-mcp: Instructions file for Claude Code