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/sgl-project/sglang/debug-distributed-hangnpx skills add sgl-project/sglang --skill debug-distributed-hanggit clone --depth 1 https://github.com/sgl-project/sglangWrote 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/sgl-project/sglang/debug-distributed-hang)<a href="https://agentmods.dev/skills/sgl-project/sglang/debug-distributed-hang"><img src="https://agentmods.dev/badge/skills/sgl-project/sglang/debug-distributed-hang.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.00085 | $0.02427 |
| Opus 5 | $0.00043 | $0.01213 |
| Sonnet 5 | $0.00017 | $0.00485 |
| Haiku 4.5 | $0.00009 | $0.00243 |
Grade A, and why
debug-distributed-hang 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging Distributed Hangs in SGLang
Overview
Hangs in distributed inference happen when ranks diverge in state, causing collective operations (AllGather, AllReduce, Broadcast, Barrier) to deadlock. Common causes:
- Size mismatch: ranks pass different tensor sizes to a collective
- Branch divergence: one rank enters a collective, another skips it
- Cascading state drift: a small non-determinism (e.g., floating-point) propagates into different batch structures
- Resource exhaustion: one rank OOMs or crashes, others wait forever
Prerequisites
- py-spy:
pip install py-spyor system package. Requires root orCAP_SYS_PTRACEto attach to running processes. - cuda-gdb: Ships with the CUDA toolkit. Ensure it's on your
PATH.
Step 1: Confirm and Locate the Hang
1a. Watchdog / py-spy
SGLang's watchdog automatically dumps py-spy traces on timeout. Look for:
Scheduler watchdog timeout (self.watchdog_timeout=300, self.soft=False)
The py-spy dump shows the stack trace of each thread. The hanging thread is typically blocked in a CUDA synchronize or NCCL collective:
Thread (active): "MainThread"
cuStreamSynchronize (libcuda.so)
...
forward_extend (model_runner.py)
SGLang has two watchdog modes (see python/sglang/srt/utils/watchdog.py):
- Hard watchdog (
soft=False, default): dumps py-spy traces then sendsSIGQUITto kill the parent process. - Soft watchdog (
soft=True): only logs the timeout without killing the process, giving you more time to manually attach debuggers or collect coredumps.
If the watchdog doesn't trigger, manually dump:
py-spy dump --pid <scheduler_pid>
1b. NCCL Debug Logging
export NCCL_DEBUG=INFO
export NCCL_DEBUG_SUBSYS=COLL
Look for the last collective logged before the hang. Mismatched sizes show up as one rank waiting and another never entering.
1c. CUDA Coredump
When a process hangs, you can trigger a GPU coredump on demand to see which kernel is stuck. Set these env vars before launching:
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 · 249 lines · 85 tokens per session scan A b2287588e589
debug-distributed-hang is a skill published in the GitHub repository sgl-project/sglang (34,054 stars, last pushed today), licensed Apache-2.0. It adds 85 tokens to every session and 2,427 once invoked, about $0.0004 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
perf-host-analysis
Analyze host/CPU overhead in TensorRT-LLM inference from nsys traces. Detect whether host overhead is the bottleneck using GPU idle ratio, host prep exposed ratio, and per-phase evidence. For regressions, isolate forward steps via allreduce/NVTX patterns, compare host operation breakdowns across versions, and identify…
perf-host-optimization
Profiles and optimizes TensorRT-LLM host/CPU overhead using lineprofiler (with nsys support planned). Runs iterative profile-analyze-optimize-validate rounds. Use when GPU utilization is low or optimizing PyExecutor throughput.
mooncake-api
Help users work with the Mooncake Python APIs for distributed storage and high-performance data transfer. Use when working with Mooncake Store (distributed KV cache), Transfer Engine (RDMA/TCP transfers), service setup (master, metadata server), PyTorch tensors in the Store, zero-copy/buffer management, batch…
mooncake-troubleshoot
Automatically diagnose Mooncake deployment and runtime issues. Checks services (mooncakemaster, metadata server), RDMA devices, environment variables, connectivity, memory limits, object integrity, and analyzes logs for common error patterns. Use when Mooncake deployment fails, services won't start, connections fail…
release-notes
Draft concise release notes.
mooncake-ci-local
Run Mooncake pre-PR local validation through scripts/runcitest.sh. Use this skill whenever the user wants to validate a branch before opening or submitting a PR, run local CI, run ci test, check changes before PR, reproduce GitHub Actions locally, or force a full pre-submit verification. Trigger on phrases like "提交 PR…