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/hkuds/cli-anything/cli-anything-lldbnpx skills add HKUDS/CLI-Anything --skill cli-anything-lldbgit clone --depth 1 https://github.com/HKUDS/CLI-AnythingWrote 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/hkuds/cli-anything/cli-anything-lldb)<a href="https://agentmods.dev/skills/hkuds/cli-anything/cli-anything-lldb"><img src="https://agentmods.dev/badge/skills/hkuds/cli-anything/cli-anything-lldb.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 | $0.00016 | $0.01729 |
| Opus 5 | $0.00008 | $0.00864 |
| Sonnet 5 | $0.00003 | $0.00346 |
| Haiku 4.5 | $0.00002 | $0.00173 |
Grade A, and why
cli-anything-lldb 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 4d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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 close
Debug 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.json
or:
cli-anything-lldb dap
cli-anything-lldb dap --profile /path/to/stop-rules.json
The 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.
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.
- 4d ago First seen · 169 lines · 16 tokens per session scan A a8a832e20cae
cli-anything-lldb is a skill published in the GitHub repository HKUDS/CLI-Anything (48,809 stars, last pushed 13d ago), licensed Apache-2.0. It adds 16 tokens to every session and 1,729 once invoked, about $0.0001 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-30.
Other skills, from other repositories
freya
Freya Rust GUI framework best practices, patterns, and conventions. Use when writing Freya components, hooks, elements, or working on a Freya project.
frame-data-rollup
A native Remotion data frame — bars grow from zero by real data via spring physics while the figures roll 0→target in sync. The numbers come alive in a way a static HTML chart can't.
dbg
Debug applications using the dbg CLI debugger. Supports Node.js (V8/CDP), Bun (WebKit/JSC), Python (debugpy/DAP), Java (JDWP/DAP), and native code via LLDB (DAP). Use when: (1) investigating runtime bugs by stepping through code, (2) inspecting variable values at specific execution points, (3) setting breakpoints and…
example-project
Use the BazelApp example project for testing XcodeBazelMCP tools end-to-end. Reference when building, running, testing iOS/macOS targets, or validating device and simulator workflows against a real Bazel workspace.
swift-agent-debug-log
Instrument Swift/iOS apps for Cursor DEBUG MODE: NDJSON hypothesis logs on the host or simulator Documents. Use with XcodeBazelMCP agentdebug tools (clear, read, pull, repro) instead of Read/deletefile on host paths from sim code.
tool-handler-development
Create or modify Bazel MCP tool handlers. Use when adding new tools, editing tool definitions, creating handler modules, or working with files under src/tools/handlers/.