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.
curl -O https://raw.githubusercontent.com/soundbytelabs/sbl-debugger-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/soundbytelabs/sbl-debugger-mcpWrote 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/instructions/soundbytelabs/sbl-debugger-mcp/claude-md)<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="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.01316 | $0.01316 |
| Opus 5 | $0.00658 | $0.00658 |
| Sonnet 5 | $0.00263 | $0.00263 |
| Haiku 4.5 | $0.00132 | $0.00132 |
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 7d 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 — 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
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.
- 7d ago First seen · 107 lines · 1,316 tokens per session scan A 03440c192c9a
sbl-debugger-mcp CLAUDE.md is an instructions file published in the GitHub repository soundbytelabs/sbl-debugger-mcp (0 stars, last pushed 6mo ago), licensed MIT. It adds 1,316 tokens to every session, about $0.0066 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.