fuzzing-dictionary

Create and manage fuzzing dictionaries for libFuzzer, AFL++, and cargo-fuzz.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/balic-AI-ML-R-D-Resources/eliza_autonomous_agents --skill fuzzing-dictionary-balic-ai-ml-r-d-resources
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fuzzing-dictionary
Source: https://github.com/balic-AI-ML-R-D-Resources/eliza_autonomous_agents/tree/main/packages/skills/skills/testing-handbook-skills/skills/fuzzing-dictionary
Command: npx skills add https://github.com/balic-AI-ML-R-D-Resources/eliza_autonomous_agents --skill fuzzing-dictionary-balic-ai-ml-r-d-resources

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fuzzing dictionaries provide domain-specific tokens, magic strings, and protocol keywords to guide mutation-based fuzzers, helping reach deeper code paths and bypass preliminary validations.

Core Features & Use Cases

  • Provide tokens as quoted strings and key-value pairs to steer fuzzers across JSON, XML, config parsers, and CLI tools.
  • Support hex escapes and cross-tool compatibility with libFuzzer, AFL++, and cargo-fuzz.
  • Enable generation sources from headers, man pages, and binary strings to broaden surface coverage.

Quick Start

Create a dictionary file containing quoted tokens and pass it to your fuzzer with the -dict option to start guiding mutations.

Frequently Asked Questions about fuzzing-dictionary

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

FAQPage Schema
How do I create a fuzzing dictionary to improve coverage for my parser?

A fuzzing dictionary provides domain-specific tokens and magic strings as quoted strings with hex escapes to guide mutation-based fuzzers, helping reach deeper code paths and bypass preliminary validations.

Can I use the same fuzzing dictionary with libFuzzer and AFL++?

Yes, the dictionary syntax using quoted strings and hex escapes supports cross-tool compatibility, allowing you to pass the same dictionary file to libFuzzer, AFL++, and cargo-fuzz.

How do I generate fuzzing dictionaries from existing binary files and headers?

You can generate fuzzing dictionaries by extracting tokens from headers, man pages, and binary strings to broaden surface coverage for your specific file format or protocol handler.

What is the best way to guide automated input mutations for JSON and XML parsers?

Providing tokens as quoted strings and key-value pairs in a dictionary steers mutation-based fuzzers to target specific JSON, XML, and config file parsers effectively.

Why does my fuzzer get stuck and fail to bypass preliminary validations?

Without a fuzzing dictionary containing domain-specific tokens and protocol keywords, your fuzzer lacks the targeted input needed to bypass preliminary validations and reach deeper code paths.

Do I need a specific dictionary syntax format for cargo-fuzz?

Yes, cargo-fuzz requires dictionary syntax with quoted strings and hex escapes to properly parse and utilize the tokens for guiding automated input mutations.