syzkaller is an automated fuzzer that generates kernel activity and uses code coverage to find bugs in operating-system kernels. It is used by kernel developers and security researchers to test Linux and other supported kernels for vulnerabilities and failures. The catalogue add-ons help coding agents operate or use syzkaller.
Borrowing it
Nothing to install: this file belongs to google/syzkaller. 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/google/syzkaller/master/.agents/skills/linux-config-update/SKILL.mdgit clone --depth 1 https://github.com/google/syzkallerWrote 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/google/syzkaller/linux-config-update)<a href="https://agentmods.dev/skills/google/syzkaller/linux-config-update"><img src="https://agentmods.dev/badge/skills/google/syzkaller/linux-config-update/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/google/syzkaller/linux-config-update"><img src="https://agentmods.dev/badge/skills/google/syzkaller/linux-config-update.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.00085 | $0.02385 |
| Opus 5.5 | $0.00034 | $0.00954 |
| Sonnet 5.5 | $0.00017 | $0.00477 |
| Haiku 4.5 | $0.00009 | $0.00238 |
Grade A, and why
linux-config-update 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 3d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Updating Linux Kernel Configs (dashboard/config/linux)
Use this skill when modifying dashboard/config/linux/ — whether enabling new CONFIG_* options,
updating kernel tags for a new Linux release, adding new instances/fragments, or regenerating
.config files.
First, read dashboard/config/linux/README.md for the
main.yml and bits/*.yml declarative syntax, instance features (baseline, base-config,
nonoise, reduced, vX.Y version tags), and how tools/syz-kconf
generates <name>.config and <name>-base.config.
1. Running make configs (Always Use syz-env!)
[!IMPORTANT] Always run config generation inside
./tools/syz-env. Kernel Kconfig evaluates compiler capabilities (cc-option,CC_VERSION_TEXT,CLANG_VERSION,GCC_VERSION, rustc/bindgen availability, etc.). Running outsidesyz-envuses host compilers and produces massive, unintended diffs across all.configfiles. Never manually edit generated*.configfiles.
Fast Iteration with INSTANCE=
A full make configs run checks out multiple kernel trees (upstream, linux-next, stable, Android,
ChromeOS) and generates ~80 configs, which is very slow.
When testing new options or debugging a failure, iterate on individual instances first using
INSTANCE=<name> (or INSTANCE=<name>-base for the baseline config):
# Quick check on a single upstream x86_64 instance:
CI=true ./tools/syz-env make configs SOURCEDIR=$KERNEL_PATH INSTANCE=upstream-apparmor-kasan
# Check older stable/android/arch/sanitizer instances to verify version and arch constraints:
CI=true ./tools/syz-env make configs SOURCEDIR=$KERNEL_PATH INSTANCE=stable-5.15-kasan
CI=true ./tools/syz-env make configs SOURCEDIR=$KERNEL_PATH INSTANCE=upstream-s390-kasan
CI=true ./tools/syz-env make configs SOURCEDIR=$KERNEL_PATH INSTANCE=upstream-kmsan
Once single-instance checks pass, run the full command without INSTANCE= to update all
affected .config files before committing:
CI=true ./tools/syz-env make configs SOURCEDIR=$KERNEL_PATH
Remove any untracked dashboard/config/linux/*.config.tmp files if left behind.
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.
- 3d ago First seen · 155 lines · 85 tokens per session scan A 884971b3dbc6
linux-config-update is a skill published in the GitHub repository google/syzkaller (6,383 stars, last pushed today), licensed Apache-2.0. It adds 85 tokens to every session and 2,385 once invoked, about $0.0003 per session on Opus 5.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-10-26.
Other skills, from other repositories
performing-api-fuzzing-with-restler
Uses Microsoft RESTler to perform stateful REST API fuzzing by automatically generating and executing test sequences that exercise API endpoints, discover producer-consumer dependencies between requests, and find security and reliability bugs. The tester compiles an OpenAPI specification into a RESTler fuzzing…
fizz
Generate Echidna/Medusa-compatible Solidity fuzz suites from Foundry or Hardhat projects. Trigger on "fizz", "generate fuzz suite", "build fuzz harness", "stateful fuzzing", "fuzzing harness", "property testing", and "invariant suite".
performing-fuzzing-with-aflplusplus
Perform coverage-guided fuzzing of compiled binaries using AFL++ (American Fuzzy Lop Plus Plus) to discover memory corruption, crashes, and security vulnerabilities. The tester instruments target binaries with afl-cc/afl-clang-fast, manages input corpora with afl-cmin and afl-tmin, runs parallel fuzzing campaigns with…
verify-ui-change-in-cloud
Verifies user-facing Warp client changes by spawning a cloud agent with computer use to test Warp. Use only when the user explicitly requested computer-use verification or accepted an offer to run it, and ONLY in non-sandboxed environments and local environments. Triggers a cloud agent that runs the test-warp-ui skill.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
fizz-convert
Convert English-language properties in PROPERTIES.md (produced by the Fizz skill) into Solidity assertions inside the existing fuzz harness, then flip their checkboxes. Trigger on "fizz-convert", "convert properties", "implement properties from PROPERTIES.md", "convert PROPERTIES.md to Solidity".