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 skills add jasonkneen/lazar --skill propose-kernel-patchgit clone --depth 1 https://github.com/jasonkneen/lazarWrote 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/jasonkneen/lazar/propose-kernel-patch)<a href="https://agentmods.dev/skills/jasonkneen/lazar/propose-kernel-patch"><img src="https://agentmods.dev/badge/skills/jasonkneen/lazar/propose-kernel-patch/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jasonkneen/lazar/propose-kernel-patch"><img src="https://agentmods.dev/badge/skills/jasonkneen/lazar/propose-kernel-patch.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00744 |
| Opus 5.5 | $0.00000 | $0.00298 |
| Sonnet 5.5 | $0.00000 | $0.00149 |
| Haiku 4.5 | $0.00000 | $0.00074 |
Grade A, and why
propose-kernel-patch 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 2mo 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
propose-kernel-patch
When you identify a change that needs to happen in the immutable kernel (bin/lazar or src/), you cannot apply it yourself — sandbox-exec blocks writes there, and chflags uchg blocks them at the OS level too. Instead, stage a complete proposal in workspace/ that the user can review and apply with one command.
When to use
- You found a bug in the kernel (e.g. error path doesn't emit structured output, missing flag, incorrect timeout).
- You need a new kernel feature (e.g. a new CLI flag, a new event type in the stream).
- You want to update a seed skill (those are baked into the binary at compile time).
- You can articulate the patch precisely and it's small enough to review.
Do NOT use this for things that should be skills. The kernel does ONE thing — runs bash + records events. Adding behavior to skills is always preferred.
How to use
-
Pick a short kebab-case slug for the proposal (e.g.
http-error-emit,add-resume-flag). -
Create the proposal directory:
mkdir -p $LAZAR_HOME/workspace/proposals/<slug>/src/src mkdir -p $LAZAR_HOME/workspace/proposals/<slug>/src/seed-skills -
Copy the FULL current kernel as the starting point:
cp -R $LAZAR_HOME/src/. $LAZAR_HOME/workspace/proposals/<slug>/src/ -
Apply your changes inside
$LAZAR_HOME/workspace/proposals/<slug>/src/:# edit src/src/main.rs, src/sandbox.sb, src/seed-skills/<...> as needed -
Write a README explaining what changed and why:
cat > $LAZAR_HOME/workspace/proposals/<slug>/README.md <<'EOF' # <slug> ## Summary <one paragraph: what the change does> ## Why <observed problem or new capability needed> ## Files changed - src/src/main.rs (lines ~X-Y): <what> - src/seed-skills/...: <what> ## Risk <what could break, what to test after applying> EOF -
Tell the user:
I've staged a kernel patch at $LAZAR_HOME/workspace/proposals/<slug>/. Review with: diff -u --recursive $LAZAR_HOME/src $LAZAR_HOME/workspace/proposals/<slug>/src Apply with: bash $LAZAR_HOME/scripts/kernel-apply.sh <slug>
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.
- 2mo ago First seen · 67 lines · 0 tokens per session scan A e76d9b8c0a74
propose-kernel-patch is a skill published in the GitHub repository jasonkneen/lazar (31 stars, last pushed 21d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 744 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.