Fuzz Rust projects with cargo-fuzz
Set up and run cargo-fuzz — harness writing, nightly toolchain, sanitizers, coverage, crash triage
- What
- Set up and run cargo-fuzz — harness writing, nightly toolchain, sanitizers, coverage, crash triage
- Cost
- Free
- Needs
- Rust and Cargo via rustup, the nightly toolchain (rustup install nightly), then cargo install cargo-fuzz. Authorized testing only — your own code or authorized assessments.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — ⚠️ Security warning / Avertissement de sécurité — AUTHORIZED USE ONLY / USAGE AUTORISÉ UNIQUEMENT: Trail of Bits' cargo-fuzz guide — the standard fuzzer for Cargo-based Rust projects: install the nightly toolchain and cargo-fuzz, write `fuzz_target!` harnesses (library-crate structure, harness do/don't rules, structure-aware fuzzing with the `arbitrary` crate), run campaigns (sanitizer options including AddressSanitizer, dictionaries, seed corpus, re-executing crashes, interpreting output), measure coverage with llvm-tools and a report script, with a full worked example on the ogg crate and a troubleshooting table. Kept by editorial choice as a borderline case: fuzzing finds real vulnerabilities — use it on your own code or within authorized testing only. Honest caveats: requires the nightly Rust toolchain; the multi-core fuzzing feature is experimental; CC-BY-SA-4.0 licensed (share-alike). Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Fuzz Rust projects with cargo-fuzz is a free guide from Trail of Bits, the fuzzer for Cargo-based Rust projects, for authorized use only. It covers installing the nightly toolchain and cargo-fuzz, writing fuzz_target harnesses with structure and harness rules, structure-aware fuzzing with the arbitrary crate, and running campaigns with sanitizer options, dictionaries, seed corpus, crash re-execution, output interpretation, and coverage.
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: Rust and Cargo via rustup, the nightly toolchain (rustup install nightly), then cargo install cargo-fuzz. Authorized testing only — your own code or authorized assessments. Install "Fuzz Rust projects with cargo-fuzz" for me. It teaches cargo-fuzz: installation, writing fuzz_target! harnesses (library-crate structure, arbitrary-crate structure-aware fuzzing), running campaigns (sanitizers, dictionaries, corpus), reproducing and triaging crash artifacts, coverage analysis, with a worked ogg-crate example — by Trail of Bits, CC-BY-SA-4.0 licensed. Repository: https://raw.githubusercontent.com/trailofbits/skills/82fe8226252622fa807643bdca1710901198553a/plugins/testing-handbook-skills/skills/cargo-fuzz/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 "cargo-fuzz". 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 the nightly toolchain and cargo-fuzz; structure my target code as a library crate before fuzzing). 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
- It can download and install software packages.
What the scan found — excerpts from the install prompt
- installs packages — Prerequisites: Rust and Cargo via rustup, the nightly toolchain (rustup install nightly), then cargo install c · Prérequis : Rust et Cargo via rustup, la toolchain nightly (rustup install nightly), puis cargo install cargo-
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 : installs packages
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.