fuzzer

Automates coverage-guided fuzzing of C/C++, Rust, and Go targets.

155|24|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/workersio/spec --skill fuzzer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fuzzer
Source: https://github.com/workersio/spec/tree/main/plugins/fuzzer/skills/fuzzer
Command: npx skills add https://github.com/workersio/spec --skill fuzzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fuzzing native codebases is essential to identify memory-safety bugs and logic errors; this skill automates coverage-guided fuzzing across C/C++, Rust, and Go, including an audit-context-building phase, automatic harness generation, sanitized builds, fuzzing execution, and structured crash reports.

Core Features & Use Cases

  • Audit-first workflow: reads the entire codebase to locate vulnerability targets before harnessing.
  • Harness generation & builds: produces deterministic fuzz targets and builds with sanitizers for quick iteration.
  • Cross-language support: applies to C/C++, Rust, and Go with unified workflows and crash triage.
  • Use Case: when you need fast, reproducible crash reproductions and actionable findings for security audits.

Quick Start

Run the fuzzer against your codebase to start an audit-driven fuzzing campaign.

Frequently Asked Questions about fuzzer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate coverage-guided fuzzing for C++ and Rust codebases?▼

It supports fuzzing across C/C++, Rust, and Go targets, automatically generating harness templates, building with sanitizers, and producing reproducible crash reports for unified triage.

Can I generate fuzz harnesses automatically for Go security audits?▼

Yes, the workflow reads the codebase to locate vulnerability targets and produces deterministic fuzz targets for Go, enabling quick iteration during security audits.

Do I need AFL++ or libFuzzer installed to run fuzzing campaigns?▼

Yes, an AFL++ or libFuzzer-style toolchain is required to execute coverage-guided fuzzing campaigns, run sanitized builds, and capture reproducible crashes.

What is the best way to triage memory-safety bugs found during fuzzing?▼

The best way to triage memory-safety bugs is using the structured crash reports and reproducible crash reproductions generated after executing sanitized fuzzing campaigns across native codebases.

Does audit-driven fuzzing work differently from standard fuzz testing?▼

Audit-driven fuzzing differs from standard fuzz testing by reading the entire codebase to locate vulnerability targets before generating harnesses, resulting in more targeted and actionable security findings.