fuzzing-dictionary

Generate fuzzing dictionaries with domain-specific tokens for libFuzzer, AFL++, and cargo-fuzz.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/ofelixdev/cc-kit --skill fuzzing-dictionary-ofelixdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fuzzing-dictionary
Source: https://github.com/ofelixdev/cc-kit/tree/main/template/skills/fuzzing-dictionary
Command: npx skills add https://github.com/ofelixdev/cc-kit --skill fuzzing-dictionary-ofelixdev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps fuzzing tools generate more effective test inputs by providing domain-specific tokens, leading to deeper code coverage and faster bug discovery.

Core Features & Use Cases

  • Targeted Input Generation: Guides fuzzers with keywords, magic bytes, and format-specific strings.
  • Improved Coverage: Helps bypass initial checks and reach complex code paths.
  • Use Case: When fuzzing a custom network protocol parser, use this Skill to provide a dictionary of valid commands, headers, and data types to uncover vulnerabilities more efficiently.

Quick Start

Use the fuzzing-dictionary skill to create a dictionary file for fuzzing a PNG parser.

Frequently Asked Questions about fuzzing-dictionary

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

FAQPage Schema
How do I generate a fuzzing dictionary for a specific file format parser?

Generate a fuzzing dictionary by extracting domain-specific tokens, magic bytes, and format-specific strings from headers, binaries, and man pages. This targeted input generation guides fuzzers to bypass initial checks and reach complex code paths in format-specific parsers.

Why does my fuzzer get stuck and fail to reach deeper code paths?

Fuzzers get stuck without domain-specific tokens to bypass initial input validation. Providing a fuzzing dictionary with valid keywords and magic bytes helps mutation strategies bypass early checks, leading to deeper code coverage and faster bug discovery.

Does this fuzzing dictionary tool work with libFuzzer and AFL++?

Yes, the generated fuzzing dictionaries support integration with libFuzzer, AFL++, and cargo-fuzz. This compatibility enhances input mutation strategies across these popular fuzzing frameworks to improve vulnerability research.

What is the best way to improve code coverage when fuzzing a custom network protocol?

The best way to improve code coverage is using a fuzzing dictionary containing valid commands, headers, and data types specific to your custom network protocol. Targeted input generation efficiently uncovers vulnerabilities in format-specific code.

Can I extract tokens from binaries and man pages to build a fuzzing dictionary?

Yes, you can extract tokens from binaries and man pages to build a fuzzing dictionary. The skill includes techniques for extracting domain-specific tokens from these sources to guide fuzzers towards deeper code paths.

When do I need a fuzzing dictionary for vulnerability research?

You need a fuzzing dictionary when targeting parsers and format-specific code to uncover vulnerabilities. It provides domain-specific tokens that guide fuzzers past initial checks, resulting in deeper code coverage and faster bug discovery.