← Explore all skills

TESTING / trailofbits

Fuzzing Dictionaries

Build targeted token dictionaries from parser expectations and compare their effect on coverage.

“Builds and applies fuzzing dictionaries so a fuzzer can produce the keywords, magic bytes, and tokens a target expects. Covers extracting tokens from source, headers,”

01 / THE REASONING

Why this made the selection.

  • The skill builds a token dictionary for a fuzzer. It says to skip that when the target is a pure algorithm or the corpus is already covering the code.
  • libFuzzer, AFL++, and cargo-fuzz are the tools it wires the file into. go-fuzz is called out as having no dictionary flag.
  • The definition combines source/header/binary extraction, escape syntax and engine-specific loading, with coverage comparison used to judge usefulness.
  • Reach parser branches guarded by protocol keywords or file signatures

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • plugins/testing-handbook-skills/skills/fuzzing-dictionary/SKILL.md
  • LICENSE
  • README.md

Our findings

  • The dictionary is a local text file passed to a fuzzer the user already has. The skill does not phone a service and does not start the fuzzer itself.
  • It says to skip the technique for pure algorithms, for targets with no keyword checks, and when coverage is already high.
  • go-fuzz is not given a dictionary flag here. The file does not claim a dictionary replaces a seed corpus.
  • The definition combines source/header/binary extraction, escape syntax and engine-specific loading, with coverage comparison used to judge usefulness.

Not established by this review

  • The resource was not executed and its tools were not called.
  • No dictionary was generated and no fuzzer was started.
  • No skill execution, authenticated service operation, or outcome benchmark was performed.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Add a skill to your workflow.

Upstream setup instructions ↗

DOCUMENTED COMMAND

npx skills add trailofbits/skills/plugins/testing-handbook-skills/skills/fuzzing-dictionary

Run in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above.

Optional: install the reviewed revision

Keeps the original source and installer version where recorded, while leaving your AI tools and installation scope for you to choose.

npx skills add https://github.com/trailofbits/skills/tree/8e54050ae63c2f62224c35b1616efe71865b4777/plugins/testing-handbook-skills/skills/fuzzing-dictionary
  1. Install the pinned skill directory interactively, retaining its bundled references and scripts.
  2. Inspect actual comparisons/specifications, select atomic tokens and encode binary values with supported escapes.
  3. Validate that the engine loads the dictionary, then compare corpus coverage under comparable budgets.

Before you start

  • A working instrumented fuzz target
  • A fuzzer supporting the selected dictionary format

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. Pinned skill definition ↗Checked

    https://github.com/trailofbits/skills/blob/8e54050ae63c2f62224c35b1616efe71865b4777/plugins/testing-handbook-skills/skills/fuzzing-dictionary/SKILL.md

    Supports: summary, whySelected, bestFor, limitations, install, access, review

  2. https://github.com/trailofbits/skills/blob/8e54050ae63c2f62224c35b1616efe71865b4777/README.md

    Supports: install

  3. CC-BY-SA-4.0 licence ↗Checked

    https://github.com/trailofbits/skills/blob/8e54050ae63c2f62224c35b1616efe71865b4777/LICENSE

    Supports: license

Evidence & Ask