MCP Debugger
debugmcp/mcp-debugger
A skill your agent uses when investigating a bug, failing test, or unexpected runtime behavior and the mcp-debugger MCP server is available — drives real step-through debuggers (breakpoints, stack…
Stateful LLDB debugging via LLDB Python API. An agent skill from HKUDS/CLI-Anything.
Install CLI Anything Lldb
$ npx skills add HKUDS/CLI-Anything --skill cli-anything-lldb -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install HKUDS/CLI-Anything cli-anything-lldb --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/HKUDS/CLI-Anything.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cli-anything-lldb .claude/skills/cli-anything-lldb && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cli-anything-lldb" agent skill from https://github.com/HKUDS/CLI-Anything/tree/main/skills/cli-anything-lldb into .claude/skills/cli-anything-lldb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-anything-lldb", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/HKUDS/CLI-Anything/tree/main/skills/cli-anything-lldbType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add HKUDS/CLI-Anything --skill cli-anything-lldb -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install HKUDS/CLI-Anything cli-anything-lldb --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HKUDS/CLI-Anything.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/cli-anything-lldb .agents/skills/cli-anything-lldb && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cli-anything-lldb" agent skill from https://github.com/HKUDS/CLI-Anything/tree/main/skills/cli-anything-lldb into .agents/skills/cli-anything-lldb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-anything-lldb", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add HKUDS/CLI-Anything --skill cli-anything-lldb -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install HKUDS/CLI-Anything cli-anything-lldb --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HKUDS/CLI-Anything.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/cli-anything-lldb .cursor/skills/cli-anything-lldb && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cli-anything-lldb" agent skill from https://github.com/HKUDS/CLI-Anything/tree/main/skills/cli-anything-lldb into .cursor/skills/cli-anything-lldb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-anything-lldb", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/HKUDS/CLI-Anything.git --path skills/cli-anything-lldb--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add HKUDS/CLI-Anything --skill cli-anything-lldb -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install HKUDS/CLI-Anything cli-anything-lldb --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HKUDS/CLI-Anything.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/cli-anything-lldb .gemini/skills/cli-anything-lldb && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cli-anything-lldb" agent skill from https://github.com/HKUDS/CLI-Anything/tree/main/skills/cli-anything-lldb into .gemini/skills/cli-anything-lldb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-anything-lldb", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install HKUDS/CLI-Anything cli-anything-lldbInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add HKUDS/CLI-Anything --skill cli-anything-lldb -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/HKUDS/CLI-Anything.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/cli-anything-lldb .github/skills/cli-anything-lldb && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cli-anything-lldb" agent skill from https://github.com/HKUDS/CLI-Anything/tree/main/skills/cli-anything-lldb into .github/skills/cli-anything-lldb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-anything-lldb", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add HKUDS/CLI-Anything --skill cli-anything-lldb -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install HKUDS/CLI-Anything cli-anything-lldb --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HKUDS/CLI-Anything.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/cli-anything-lldb .opencode/skills/cli-anything-lldb && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cli-anything-lldb" agent skill from https://github.com/HKUDS/CLI-Anything/tree/main/skills/cli-anything-lldb into .opencode/skills/cli-anything-lldb/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-anything-lldb", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
cli-anything-lldb- GitHub stars
- 52k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 549 words
- Files
- 1
- Skills in repo
- 78
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Stateful LLDB debugging via LLDB Python API. An agent skill from HKUDS/CLI-Anything.
- Tasks that involve Debugging
- SKILL.md covers Capabilities, Quick Commands, Debug Adapter Protocol and Command Groups, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Responsive design
What it does
CLI Anything Lldb is an agent skill from HKUDS/CLI-Anything. Stateful LLDB debugging via LLDB Python API
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Debugging and Responsive design. It works with Python. The repository describes itself as: "CLI-Anything: Making ALL Software Agent-Native" -- CLI-Hub: https://clianything.cc/. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Debugging
- Tasks that involve Responsive design
Example prompts
- “/cli-anything-lldb”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit 34f5195. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
CLI Anything Lldb loads about 1.7k tokens when it runs. Until then it costs about 15 tokens; SKILL.md has 549 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from HKUDS/CLI-Anything at commit 34f5195, republished under its Apache-2.0 licence (© HKUDS). 549 words, ~1,709 tokens.
Download SKILL.mdSave it as
.claude/skills/cli-anything-lldb/SKILL.md (or your agent's skills folder).- name
- cli-anything-lldb
- description
- Stateful LLDB debugging via LLDB Python API
- version
- 1.0.0
- command
- cli-anything-lldb
- install
- pip install cli-anything-lldb
- requires
- lldb (Python bindings), click>=8.0, prompt-toolkit>=3.0
- categories
- debugging, native, lldb
LLDB CLI Skill
Use this CLI to run structured LLDB debugging workflows with JSON output.
Capabilities
- Create debug target from executable path
- Launch process or attach by pid/name
- Manage breakpoints (set/list/delete/enable/disable)
- Inspect threads, frames, locals, and backtrace
- Evaluate expressions in current frame
- Read/find process memory
- Load core dumps
- Interactive REPL with persistent session state
- Formal stdio Debug Adapter Protocol server for AI/editor clients
Quick Commands
cli-anything-lldb --json target create --exe /path/to/exe
cli-anything-lldb --json process launch --arg foo --arg bar
cli-anything-lldb --json breakpoint set --function main
cli-anything-lldb --json breakpoint set --function PluginEntry --allow-pending
cli-anything-lldb --json process continue
cli-anything-lldb --json process interrupt
cli-anything-lldb --json thread backtrace --limit 20
cli-anything-lldb --json frame locals
cli-anything-lldb --json expr "myVar"
cli-anything-lldb --json memory read --address 0x1000 --size 64
cli-anything-lldb --json session closeDebug Adapter Protocol
Use the DAP entry point when an AI client needs a real debug adapter lifecycle instead of shelling out separate CLI commands:
cli-anything-lldb-dap
cli-anything-lldb-dap --profile /path/to/stop-rules.jsonor:
cli-anything-lldb dap
cli-anything-lldb dap --profile /path/to/stop-rules.jsonThe DAP server speaks stdio Content-Length frames and must have exclusive
stdout. Do not print logs to stdout around it. Supported requests include
initialize, launch, attach, configurationDone, setBreakpoints,
setFunctionBreakpoints, threads, stackTrace, scopes, variables,
setVariable, evaluate, continue, pause, next, stepIn, stepOut,
source, loadedSources, readMemory, modules, exceptionInfo,
disassemble, and disconnect.
DAP variables can expose child references for structs/classes/arrays. Use
setVariable only while stopped; LLDB may reject writes to optimized-out or
read-only values.
For long-running GUI debuggees, DAP continue is non-blocking from the client's
point of view: the adapter sends the response and continued event first, then
waits for LLDB on a background thread. DAP pause uses LLDB async interrupt.
If an agent needs to change breakpoints while the debuggee is running, the
adapter interrupts first and waits for a stopped state before mutating LLDB
breakpoints; if the target does not stop in time, retry after an explicit
pause/stopped cycle.
For GUI apps that stop on debugger-internal startup or shader-JIT breakpoints,
launch and attach accept the non-standard boolean argument
autoContinueInternalBreakpoints. Enable it only when those internal stops are
noise for the task; the adapter emits an output event before auto-continuing.
For target-specific noise, prefer structured stop rules through inline
stopRules or an external stopRuleProfile/--profile JSON file. Rules can
match by reason, module, function, and/or regex, then either stop with
clear cliAnythingStop.origin metadata or continue automatically. Use
profiles for apps such as C4D so their NVIDIA shader-JIT/startup traps live
outside the generic adapter.
DAP stopped events include body.cliAnythingStop.origin: manualPause for a
client pause request, internalTrap for a matched internal rule, and debuggee
for ordinary program stops. Existing cli-anything-lldb-dap processes do not
hot-load new code or profile contents; restart the adapter and re-attach or
re-launch before expecting new rules to apply.
Show full SKILL.md (172 more words)Show less
Command Groups
target
cli-anything-lldb --json target create --exe /path/to/exe [--arch x86_64]
cli-anything-lldb --json target infoprocess
cli-anything-lldb --json process launch [--arg ARG ...] [--env KEY=VALUE ...] [--cwd DIR] [--stop-at-entry]
cli-anything-lldb --json process attach --pid 1234
cli-anything-lldb --json process attach --name myapp --wait-for
cli-anything-lldb --json process continue
cli-anything-lldb --json process interrupt
cli-anything-lldb --json process detach
cli-anything-lldb --json process infobreakpoint
cli-anything-lldb --json breakpoint set --function main
cli-anything-lldb --json breakpoint set --file main.c --line 42 --condition "i > 10"
cli-anything-lldb --json breakpoint set --function LateLoadedSymbol --allow-pending
cli-anything-lldb --json breakpoint list
cli-anything-lldb --json breakpoint delete --id 1
cli-anything-lldb --json breakpoint enable --id 1
cli-anything-lldb --json breakpoint disable --id 1thread / frame / step
cli-anything-lldb --json thread list
cli-anything-lldb --json thread select --id 11111
cli-anything-lldb --json thread backtrace --limit 50
cli-anything-lldb --json frame select --index 0
cli-anything-lldb --json frame info
cli-anything-lldb --json frame locals
cli-anything-lldb --json step over
cli-anything-lldb --json step into
cli-anything-lldb --json step outexpr / memory / core
cli-anything-lldb --json expr "argc"
cli-anything-lldb --json memory read --address 0x1000 --size 128
cli-anything-lldb --json memory find "needle" --start 0x1000 --size 4096
cli-anything-lldb --json core load --path /path/to/coreAgent Usage Notes
- Prefer
--jsonfor all automated flows. - Separate non-REPL invocations share a persistent session daemon by default.
- Use
--session-file PATHorCLI_ANYTHING_LLDB_SESSION_FILEto pin an explicit session for a task. - Run
cli-anything-lldb --json session closewhen finished so attached processes detach and launched debuggees are cleaned up. - Use REPL when a human-like interactive shell is more convenient, not because persistence requires it.
- Unresolved CLI breakpoints fail by default; pass
--allow-pendingonly when a future module/symbol load is expected. - DAP unresolved breakpoints use protocol semantics:
verified: falseuntil resolved. - DAP
continueis non-blocking for long-running GUI processes, and DAPpauseuses async interrupt. - DAP breakpoint changes during an active continue first interrupt and wait for a stopped state before mutating LLDB.
- Use DAP stop-rule profiles for app-specific internal traps; restart and re-attach/re-launch after profile changes.
memory finduses a chunked scan capped at 1 MiB per call.- Call
target createbefore process or core commands. - Expect structured errors:
{"error": "...", "type": "..."}
© HKUDS, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/cli-anything-lldb of HKUDS/CLI-Anything.
Open the folder on GitHubat commit 34f5195
Compare with similar skills
CLI Anything Lldb next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| CLI Anything Lldb this skillHKUDS/CLI-Anything | 52k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| MCP Debuggerdebugmcp/mcp-debugger | 171 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Dbgtheodo-group/debug-that | 158 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Ue Live DebuggingJasonMa0012/MooaToon | 749 | — | ~2.9k | Automated safety check: Notes | Custom licence | |
| Tilelang Debug Helpertile-ai/tilelang-ascend | 400 | — | ~1.7k | Automated safety check: Notes | MIT | |
| Debugging Techniquesancoleman/ai-design-components | 526 | — | ~3.3k | Automated safety check: Pass | MIT |
Similar skills
Dbg
theodo-group/debug-that
Debug applications using the dbg CLI debugger. An agent skill from theodo-group/debug-that.
Ue Live Debugging
JasonMa0012/MooaToon
A skill your agent uses when debugging UE C++ crashes, runtime bugs, or unexpected behavior with Rider MCP available.
Tilelang Debug Helper
tile-ai/tilelang-ascend
How to add debugging capabilities to TileLang Ascend example operators.
Debugging Techniques
ancoleman/ai-design-components
Debugging workflows for Python (pdb, debugpy), Go (delve), Rust (lldb), and Node.js, including container debugging (kubectl debug, ephemeral containers) and production-safe debugging techniques with…
Gdb
mohitmishra786/low-level-dev-skills
GDB debugger skill for C/C++ programs. An agent skill from mohitmishra786/low-level-dev-skills.
More from HKUDS/CLI-Anything
All 78 skills in this repoCLI-Anything for Codex
HKUDS/CLI-Anything
Lets Codex build, refine, test, validate and list CLI-Anything harnesses for GUI applications or source repositories, following the project's full methodology.
CLI-Anything for Reasonix
HKUDS/CLI-Anything
Adapts the CLI-Anything methodology so Reasonix can build, refine, test and validate a command-line harness for an existing GUI application or source repository.
CLI-Anything for Hermes Agent
HKUDS/CLI-Anything
Guides Hermes Agent through building, refining and testing a CLI-Anything harness that wraps a GUI application or source repository in a scriptable command line.
CLI-Anything Harness Builder
HKUDS/CLI-Anything
Builds, refines, tests or validates a CLI-Anything harness that wraps a GUI application or source repository as a stateful Click CLI with JSON output and a REPL mode.
Krita CLI Harness
HKUDS/CLI-Anything
Drives Krita from the command line to create projects, add layers, apply filters, resize the canvas and export images, with JSON output for agents.
MacroCLI GUI Macros
HKUDS/CLI-Anything
Defines, lists, inspects and runs parameterized GUI macros from the command line, with the runtime choosing the execution backend.
Related
Works with
Categories
Questions about CLI Anything Lldb
What does CLI Anything Lldb do?
Stateful LLDB debugging via LLDB Python API. An agent skill from HKUDS/CLI-Anything. CLI Anything Lldb is an agent skill from HKUDS/CLI-Anything.
When should I use CLI Anything Lldb?
CLI Anything Lldb fits situations like: tasks that involve Debugging; tasks that involve Responsive design.
How do I install CLI Anything Lldb in Claude Code?
Run `npx skills add HKUDS/CLI-Anything --skill cli-anything-lldb -a claude-code`. Or copy the skill folder (skills/cli-anything-lldb in HKUDS/CLI-Anything) into .claude/skills/cli-anything-lldb in your project. Claude Code loads it when a task matches its description.
How do I install CLI Anything Lldb in Codex?
Run `npx skills add HKUDS/CLI-Anything --skill cli-anything-lldb -a codex`. Or copy the skill folder (skills/cli-anything-lldb in HKUDS/CLI-Anything) into .agents/skills/cli-anything-lldb in your project. Codex loads it when a task matches its description.
Can I use CLI Anything Lldb in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add HKUDS/CLI-Anything --skill cli-anything-lldb -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cli-anything-lldb, .gemini/skills/cli-anything-lldb, .github/skills/cli-anything-lldb and .opencode/skills/cli-anything-lldb in your project.
What does CLI Anything Lldb need to run?
SKILL.md names no scripts, command-line tools or credentials: CLI Anything Lldb is instructions for the agent only. Our summary lists: Python 3.
Does CLI Anything Lldb access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is CLI Anything Lldb safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does CLI Anything Lldb use?
CLI Anything Lldb is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does CLI Anything Lldb use?
About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to CLI Anything Lldb?
Skills that share tags, products or a category with CLI Anything Lldb: MCP Debugger (debugmcp/mcp-debugger, 171 stars), Dbg (theodo-group/debug-that, 158 stars), Ue Live Debugging (JasonMa0012/MooaToon, 749 stars) and Tilelang Debug Helper (tile-ai/tilelang-ascend, 400 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains CLI Anything Lldb?
HKUDS (a GitHub organization) maintains it in HKUDS/CLI-Anything, which has 51,696 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on September 22, 2026.
Source: HKUDS/CLI-Anything on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.