Borrowing it
Nothing to install: this file belongs to glslang/windbg-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/glslang/windbg-mcp/main/.claude/skills/live-kernel/SKILL.mdgit clone --depth 1 https://github.com/glslang/windbg-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/glslang/windbg-mcp/live-kernel)<a href="https://agentmods.dev/skills/glslang/windbg-mcp/live-kernel"><img src="https://agentmods.dev/badge/skills/glslang/windbg-mcp/live-kernel.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.00079 | $0.04293 |
| Opus 5 | $0.00039 | $0.02146 |
| Sonnet 5 | $0.00016 | $0.00859 |
| Haiku 4.5 | $0.00008 | $0.00429 |
Grade A, and why
live-kernel 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 today.
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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Live kernel and driver IOCTL work
Two ways a target is reached, and neither is "the" procedure
KDNET. Check the target is reachable before starting the tier, not by starting it — an attach
that finds nothing parks its worker in WaitForEvent(INFINITE) for the whole run and reports a
timeout that measures the environment rather than the code. What settles it is not "can I reach the
guest" but does the guest's bcdedit /dbgsettings hostip equal this debugger host's current IP,
on the port the profile names; the host IP moves between sessions. Compare the key by hash rather
than printing it.
Finding the guest is topology-specific. On the machine that paragraph was written for, the
debugger host is itself a Hyper-V guest — Get-VM does not exist and there is no local VM to start
— so the target is a sibling: it appears in the neighbour table (Get-NetNeighbor | ? LinkLayerAddress -like '00-15-5D*') and answers TCP 5985 and nothing else, ICMP and 445 being
closed, so a failed ping proves nothing there. With several neighbours the table will happily
validate the wrong guest, which is what the hostip comparison is for.
Serial, which is what the Parallels bench uses — and there KDNET is not merely unconfigured but
impossible: guests get a Parallels VirtIO Ethernet Adapter (PCI\VEN_1AF4), and 1AF4 is not
in the Debugging Tools' VerifiedNICList.xml. prlctl set <vm> --device-set net0 --adapter-type e1000 is accepted and silently ignored on ARM, leaving the guest with no network at all. Do not
spend an afternoon on it. The wiring that works is a TCP socket between two guests:
- target
serial0→tcp://localhost:2020, client;bcdedit /dbgsettings serial debugport:1 baudrate:115200 - debugger
serial0→tcp://:2020, server — thenprlctl set <vm> --device-connect serial0, or it staysstate=disconnectedand nothing binds the port, and a VM restart, or the guest never sees a COM port netstat -an | grep 2020on the Mac: a LISTEN and an ESTABLISHED pair means the wire is up- on the target,
ARM PL011 Serial Port Device (COM1)inErrorstate with no name fromGetPortNames()is correct — that is the kernel debugger owning the port
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.
- today First seen · 211 lines · 79 tokens per session scan A ede0cbad3657
live-kernel is a skill published in the GitHub repository glslang/windbg-mcp (9 stars, last pushed yesterday), licensed MIT. It adds 79 tokens to every session and 4,293 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-09-06.
Other skills, from other repositories
gke-ai-troubleshooting-tpu-dynamic-slices-monitoring
Monitors, troubleshoots, and manages GKE TPU Dynamic Slices custom resources. Use when checking TPU slice lifecycle states, troubleshooting slice provisioning failures, validating single-slice or multi-slice (JobSet) workload manifests, or safely patching stuck finalizers and disabling the slice controller. Don't use…
gke-ai-troubleshooting-tpu-vbar-oom
Diagnoses and prevents vbarcontrolagent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbarcontrolagent crashes, memory cgroup OOMs in serial console…
competition-firmware-layout
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for firmware images, partition tables, boot chains, update packages, extracted filesystems, embedded configs, and device-facing trust boundaries. Use when the user asks to unpack firmware, map partition layout, inspect bootloader or init…
doca-flow
Build and debug DOCA Flow applications on supported NVIDIA NICs/DPUs: define match/action pipes, initialize ports and representors, choose forwarding targets, validate pipes before hardware programming, read counters, match the Flow version to the installed DOCA release, and diagnose Flow API errors. Trigger on DOCA…
diagnose-driver-install
Diagnose NVIDIA driver installation failures on DeepOps-managed nodes — nvidia-smi errors, "No devices were found", DKMS build failures, or GPU pods crash-looping. Use before reinstalling anything.
catc-troubleshoot
Catalyst Center troubleshooting workflows - device unreachable investigation, client connectivity issues, interface down analysis, site-wide outage triage, wireless roaming problems, integration with pyATS for CLI-level diagnostics. Use when a device is unreachable, a user reports connectivity problems, an interface…