القائمة
Run a fuzzing campaign using AFL++ with optional seeds; supports `--custom_mutator_path` (you can write your own custom mutator and use this to execute).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Technical reference for OpenSage-ADK — a Google ADK-based framework for long-horizon, tool-heavy AI agents. Covers architecture, configuration, customization, extension, and production agent patterns.
Find testcase IDs (TESTCASE nodes) that cover a given function (METHOD node) in Neo4j.
Code coverage analysis tools. These tools help analyze and visualize code coverage for test execution, upload coverage data to Neo4j, and display coverage statistics. Available tools: run-coverage, show-coverage.
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
Standalone `mmp` executable for managing multiple MCP servers from a loaded gateway config.
Neo4j database management and query tools. These tools help interact with Neo4j databases for code analysis, graph queries, and data management. Available tools: neo4j-query.
| name | run-fuzzing-campaign |
| description | Run a fuzzing campaign using AFL++ with optional seeds; supports `--custom_mutator_path` (you can write your own custom mutator and use this to execute). |
| should_run_in_sandbox | fuzz |
| returns_json | false |
Run an AFL++ fuzzing campaign.
This tool supports custom mutators via --custom_mutator_path. You can
also write your own custom mutator (Python) and pass it in.
/bash_tools/fuzz/run-fuzzing-campaign/scripts/run_fuzzing_campaign.sh target_binary 180
/bash_tools/fuzz/run-fuzzing-campaign/scripts/run_fuzzing_campaign.sh target_binary 180 /path/to/seed1.txt /path/to/seed2.txt
/bash_tools/fuzz/run-fuzzing-campaign/scripts/run_fuzzing_campaign.sh target_binary 180 /path/to/seed.txt --custom_mutator_path /fuzz/mutator/custom_mutator.py
/bash_tools/fuzz/run-fuzzing-campaign/scripts/run_fuzzing_campaign.sh target_binary 180 /path/to/seed.txt --reset_output
Type: str
Fuzz target binary name (expected at /out/<fuzz_target>).
Type: int
Fuzzing duration in seconds (e.g., 180).
Type: list of strings
Optional seed file/dir paths.
Type: str
Optional path to a custom mutator script.
Type: bool (default: false)
Reset output and start fresh.
If you provide --custom_mutator_path, AFL++ will load the mutator from that
path. A common convention is to place it in the fuzz sandbox, e.g.:
/bash_tools/fuzz/run-fuzzing-campaign/scripts/run_fuzzing_campaign.sh target_binary 180 /path/to/seed.txt \
--custom_mutator_path /fuzz/mutator/custom_mutator.py
You can implement your own custom_mutator.py as part of your workflow and
iterate on it during fuzzing.
Returns text output (summary of fuzzing results).
fuzz
200 seconds