Run AFL++ fuzzing campaigns to discover crashes and hangs in C/C++ programs.
npx skills add https://github.com/ayehiaa/my-travel-assistant --skill aflpp-ayehiaa
Please help me install this Agent Skill. Skill: aflpp Source: https://github.com/ayehiaa/my-travel-assistant/tree/main/.agents/skills/aflpp Command: npx skills add https://github.com/ayehiaa/my-travel-assistant --skill aflpp-ayehiaa
This Skill helps you run high-throughput fuzzing campaigns that uncover crashes and hangs in C/C++ programs without needing a handcrafted single-thread fuzzer workflow.
Use case example: You maintain a C++ service that occasionally segfaults on certain inputs; you compile an AFL++-instrumented target with sanitizers, start a multi-core campaign with representative seeds, then re-execute and triage the exact crashing inputs from the crashes/ directory.
Ask the aflpp Skill to set up AFL++ and compile your C/C++ harness, then start an afl-fuzz campaign using your initial seed corpus to begin discovering crashes and coverage improvements.
High-intent search queries and answers about installing and using this skill.
Run a multi-core fuzzing campaign by compiling an instrumented C/C++ harness with an AFL++-compatible mode like afl-clang-lto, then starting afl-fuzz with a seed corpus to continuously mutate inputs and discover crashes.
Yes, you can enable ASan or UBSan during AFL++ fuzzing to detect memory corruptions and undefined behavior that may not immediately crash the instrumented target.
You can manage and minimize a fuzzing corpus by applying AFL++ corpus minimization workflows to reduce seed inputs while maintaining coverage, ensuring efficient continuous fuzzing execution.
You need to use an AFL++-compatible compile mode such as afl-clang-fast++, afl-clang-lto, or afl-g++-fast to build an instrumented harness for mutating inputs and finding crashes.
After an AFL++ fuzzing campaign discovers crashes, you re-execute and triage the exact crashing inputs directly from the crashes/ output directory to analyze the identified hangs and segfaults.
You can set environment variables like AFL_TMPDIR and AFL_FAST_CAL alongside campaign control parameters such as timeouts and execution limits to manage deterministic execution and calibration.
erenisiklarFuzz C/C++ project inputs with AFL++ to uncover defects.
KotlinIdentify root causes of Kotlin and Spring failures from stack traces and logs.
andrescardonas7Run multi-core AFL++ fuzzing campaigns for C/C++ projects with sanitizers.
ayehiaaBuild custom coverage-guided fuzzers with modular Rust components.
