Build custom fuzzers with LibAFL
Compose LibAFL's modular Rust components — observers, feedbacks, mutators, schedulers, executors — into custom fuzzers, or use it as a libFuzzer drop-in
- What
- Compose LibAFL's modular Rust components — observers, feedbacks, mutators, schedulers, executors — into custom fuzzers, or use it as a libFuzzer drop-in
- Cost
- Free
- Needs
- Linux or macOS; Clang/LLVM 15-18 and Rust installed (nightly Rust for libFuzzer compatibility mode); a fuzzing target with source access — only fuzz code you own or are authorized to test
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — ⚠️ Security research tool: only fuzz targets you own or are authorized to test. @trailofbits' guide to LibAFL, the modular Rust fuzzing library: when to choose it over libFuzzer or AFL++, drop-in libFuzzer replacement mode, and the full custom-fuzzer path — composing observers, feedbacks, objectives, mutators, schedulers and executors in Rust, crash deduplication via backtrace hashing, dictionary and auto-token fuzzing, multi-core campaigns with a TUI, compiler-wrapper instrumentation, plus complete libpng and CMake walkthroughs and a troubleshooting table. By @trailofbits, listed here with credit to its creator. Honest caveats: heavy prerequisites (Clang/LLVM 15-18, Rust, Linux/macOS); LibAFL evolves fast — pin a compatible version. License CC-BY-SA-4.0. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Build custom fuzzers with LibAFL is a free guide from Trail of Bits to LibAFL, the Rust fuzzing library, for research on targets you own or are authorized to test. It covers when to choose LibAFL over libFuzzer or AFL++, a libFuzzer mode, and the path composing observers, mutators, schedulers, and executors in Rust, with deduplication, fuzzing, campaigns, and instrumentation.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 82fe822Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: Linux or macOS; Clang/LLVM 15-18 and Rust installed (nightly Rust for libFuzzer compatibility mode); a fuzzing target with source access — only fuzz code you own or are authorized to test Install "Build custom fuzzers with LibAFL" for me. It gives the agent @trailofbits' LibAFL playbook: choosing LibAFL over libFuzzer/AFL++, drop-in libFuzzer mode, and composing modular Rust components (observers, feedbacks, mutators, schedulers, executors) into a bespoke fuzzer — crash deduplication, dictionary fuzzing, multi-core campaigns, libpng and CMake walkthroughs. CC-BY-SA-4.0 licensed. Repository: https://raw.githubusercontent.com/trailofbits/skills/82fe8226252622fa807643bdca1710901198553a/plugins/testing-handbook-skills/skills/libafl/SKILL.md Pinned version: install the code at commit 82fe8226252622fa807643bdca1710901198553a exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "libafl". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. install Clang/LLVM 15-18 and Rust, clone the LibAFL repo, build the runtime before first use). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 82fe822 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.