Inspect a paused Windows executable with x64dbg MCP
Load an authorized Windows executable, pause at a breakpoint, and collect registers, memory, disassembly, and call-stack evidence through x64dbg MCP.
npx skills add agentskillexchange/skills --skill inspect-paused-windows-executable-with-x64dbg-mcp
Invoke this workflow when a debugging agent needs reproducible evidence from a Windows executable rather than asking an operator to copy debugger panes by hand. Inputs are the authorized executable or process, target architecture, breakpoint or failing address, and a bounded inspection question. The output is a debugger-state report tied to a specific pause, with addresses and observed evidence.
What this skill actually does
Install the upstream v1.7 plugin by extracting its release archive and copying the contents of dist/ into the x64dbg root. Launch the matching x32 or x64 debugger. In the plugin configuration, use local-only binding for a local client and copy the generated bearer token into the client’s protected configuration. The documented HTTP MCP endpoint is http://localhost:9094/ for x64, or port 9095 for x32, with an Authorization bearer header. The upstream default listens on all interfaces; configure the intended bind address explicitly.
Start with GetDebugState. Use LoadBinary for the selected target, SetBreakpoint at the authorized inspection point, then run and WaitForPause. Confirm that the paused process and instruction pointer match the requested case. Collect GetAllRegisters, a bounded ReadMemory range, Disassemble, and GetCallStack. Step with StepOver only when the question requires it, recording the new instruction pointer and keeping before-and-after observations separate.
Return target identity, breakpoint, pause state, relevant registers, memory range, disassembly, call stack, and any unresolved symbols or failed calls. Retain the process in the operator’s requested state. This procedure is limited to loading, execution control, and observation; memory patching, unpacking, and general command execution are separate tasks. Tool calls use the upstream MCP interface, so MCP is the defensible framework. Source snapshot: v1.7 source. Installation, authentication enforcement, and debugger operation were not executed during discovery review.