Binary Debugging

Use this skill after engagement-scope has established the authorized target, scope evidence, environment, impact tolerance, and desired deliverable. If no brief is present, infer local/offline scope from files in the workspace and ask only for missing information that changes whether execution or instrumentation is allowed.

Prefer local, reproducible, low-impact debugging: static inspection, crash/core analysis, sanitizer output, recorded traces, and isolated lab execution. Do not attach to production processes, run unknown binaries, fuzz live services, or exercise exploit payloads unless the engagement explicitly allows that impact.

Debugging Modes

Choose one primary mode: