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 benpm/claude_lldb_mcp --skill debug-cppgit clone --depth 1 https://github.com/benpm/claude_lldb_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/skills/benpm/claude_lldb_mcp/debug-cpp)<a href="https://agentmods.dev/skills/benpm/claude_lldb_mcp/debug-cpp"><img src="https://agentmods.dev/badge/skills/benpm/claude_lldb_mcp/debug-cpp/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/benpm/claude_lldb_mcp/debug-cpp"><img src="https://agentmods.dev/badge/skills/benpm/claude_lldb_mcp/debug-cpp.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.00173 | $0.02060 |
| Opus 5.5 | $0.00069 | $0.00824 |
| Sonnet 5.5 | $0.00035 | $0.00412 |
| Haiku 4.5 | $0.00017 | $0.00206 |
Grade A, and why
debug-cpp 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging C/C++ with LLDB MCP Tools
This skill guides you through debugging compiled C/C++ programs using the LLDB MCP server. The server provides 17 specialized tools that wrap LLDB in batch mode — each tool call spawns a fresh LLDB process, so there's no persistent session state between calls. This means you need to replay setup (target + breakpoints) on each tool invocation, which the tools handle automatically via their parameters.
Step 0: Gather what you need
Before touching any tool, ask the user (or infer from context) these three things:
- Executable path — the compiled binary (absolute path is most reliable)
- What's wrong — crash, wrong output, hang, assertion failure, unexpected variable value?
- Arguments — command-line args the program needs (can be empty)
If the user only has source files, go to Build first below. If they already have a binary, skip ahead.
Build first (if no binary)
Compile with debug symbols and no optimization — without -g -O0, LLDB can't show source lines or variable names:
clang++ -g -O0 -o /abs/path/to/output /abs/path/to/source.cpp
# Multi-file:
clang++ -g -O0 -o output main.cpp helper.cpp
# CMake project:
cmake -B build -DCMAKE_BUILD_TYPE=Debug -DCMAKE_EXPORT_COMPILE_COMMANDS=ON
cmake --build build
Windows/git bash path note: LLDB on Windows accepts both Unix-style git bash paths (/c/Users/ben/proj/app) and Windows-style paths (C:\Users\ben\proj\app). Pass whichever form the user gives you — both work. Use absolute paths to avoid working-directory ambiguity.
Step 1: Confirm the environment
Call lldb_version (no parameters) to confirm LLDB is installed and reachable. If this fails, LLDB is not in PATH — on Windows, the LLVM installer must add C:\Program Files\LLVM\bin to the system PATH.
Step 2: Choose your entry point
Decide where to stop execution first based on what you're investigating:
| Scenario | Breakpoint approach |
|---|---|
| Function crashes or has wrong output | location = "function_name" |
| Bug at a specific source line | location = "/abs/path/file.cpp:42" |
| Program crashes immediately | Use lldb_analyze_crash instead of breakpoints |
| Want to start from scratch | location = "main" |
| Address you found in a crash log | location = "0x401234" |
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 · 130 lines · 173 tokens per session scan A 5bfcf1c1d050
debug-cpp is a skill published in the GitHub repository benpm/claude_lldb_mcp (3 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 173 tokens to every session and 2,060 once invoked, about $0.0007 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.
Other skills, from other repositories
cpp-pro
Writes, optimizes, and debugs C++ applications using modern C++20/23 features, template metaprogramming, and high-performance systems techniques. Use when building or refactoring C++ code requiring concepts, ranges, coroutines, SIMD optimization, or careful memory management — or when addressing performance…
memory-safety-patterns
Implement memory-safe programming with RAII, ownership, smart pointers, and resource management across Rust, C++, and C. Use when writing safe systems code, managing resources, or preventing memory bugs.
re-cpp-abi
A tool for examining compiled modern C++ programs when the original source code is unavailable. It helps recover class information, virtual function tables, exception paths, and readable names from a binary file.
cuda-c-optimization
A guide for improving CUDA C programs, which run computations on NVIDIA GPUs. It covers GPU memory access, thread-block sizing, numerical stability, and debugging.
cpp
Comprehensive C/C++ programming reference covering everything from C11-C23 and C++11-C++23, system programming, CUDA GPU computing, debugging tools, Rust interop, and advanced topics. Use for: C/C++ questions, C/C++ interview preparation, modern language features, RAII/memory management, templates/generics, CUDA…
memory-safety-patterns
Implement memory-safe programming with RAII, ownership, smart pointers, and resource management across Rust, C++, and C. Use when writing safe systems code, managing resources, or preventing memory bugs.