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/davidbuchanan314/kernel-livepatch-skill/kernel-livepatchnpx skills add DavidBuchanan314/kernel-livepatch-skill --skill kernel-livepatchgit clone --depth 1 https://github.com/DavidBuchanan314/kernel-livepatch-skillWhat 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.00000 | $0.00426 |
| Opus 5 | $0.00000 | $0.00213 |
| Sonnet 5 | $0.00000 | $0.00085 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
kernel-livepatch 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 2d 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.
What it actually says
Kernel Live-Patch Skill
The tools here allow claude to live-patch the running kernel, without requiring source or even headers.
Workflow:
- Dump the running kernel with
kdump_sections.py(this step requires root - you may need to prompt the user to invoke sudo. all other steps must be done autonomously.). This step must be done for each session, since ASLR changes on each boot. Output goes to./kdump/by default. - Load the dump into a headless ghidra project with
ghidra_load.py - Decompile+disassemble functions of interest using
ghidra_print_func.py <function_name>. Any addresses you see here are absolute, ASLR is already accounted for. Hint: Grep./kdump/kallsymsfor available symbols. - Reconstruct kernel headers using
gen_vmlinux_h.py - Devise a kernel patch strategy, and write a kernel module to perform the patching. (see ./example-module/ for an example).
- It's ok to hardcode addresses.
- You can do simple instruction patches with text_poke()
- For nontrivial hooks, use register_kprobe()
- NOTE: not all symbols are available! Grep the generated vmlinux.h to see what is. Anything defined as a macro is not present, you'll need to work around this. Some symbols may be available in
./kdump/kallsymsbut not in vmlinux.h, if they're missing BTF info. - Ideally, you should have the module revert any patches when unloaded.
- Compile the module and instruct the user to insmod it.
Additional useful tools:
- Use
read_kdump.pyto read subsections of an existing kernel dump, as raw data. - When
--disasm LENGTHis passed toghidra_print_func.py, the first positional arg is treated as an address. The Ghidra script skips decompilation and just disassembles the raw address range.
What ships with it
14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- example-module/hello.c 176 B
- example-module/kmod.h 818 B
- example-module/Makefile 197 B
- gen_vmlinux_h.py 43 KB runs code
- ghidra_load.py 2.0 KB runs code
- ghidra_print_func.py 1.8 KB runs code
- ghidra-scripts/ghidra_add_sections.py 14 KB runs code
- ghidra-scripts/ghidra_print_func.py 5.3 KB runs code
- kdump_sections.py 8.4 KB runs code
- lib/btf.py 14 KB runs code
- lib/btf2json.py 8.7 KB runs code
- lib/ghidra_run.py 1.3 KB runs code
- lib/kcore_dump.py 4.3 KB runs code
- read_kdump.py 2.6 KB runs code
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.
- 2d ago First seen · 23 lines · 0 tokens per session scan A d8de40fa0a74
kernel-livepatch is a skill published in the GitHub repository DavidBuchanan314/kernel-livepatch-skill (21 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 426 tokens. 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…