A command for scanning a Windows program for possible security weaknesses, especially unsafe memory operations and dangerous system APIs. It examines protections such as address randomisation and data-execution prevention before checking imported and used functions.

Use it to inspect a binary's security protections, find risky APIs, and focus the scan on a vulnerability category such as use-after-free or buffer overflow.

It helps find common vulnerability risks that may be missed during ordinary code review, including buffer overflows and format-string problems.

find-vuln — Command for Claude Code by SetsunaYukiOvO/x64dbg-mcp

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/SetsunaYukiOvO/x64dbg-mcp

Made for: Claude Code.

Or install x64dbg-re, the plugin that ships this one along with the rest of its 1 skill, 11 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/setsunayukiovo/x64dbg-mcp/find-vuln/github.svg)](https://agentmods.dev/commands/setsunayukiovo/x64dbg-mcp/find-vuln)

Your own site

<a href="https://agentmods.dev/commands/setsunayukiovo/x64dbg-mcp/find-vuln"><img src="https://agentmods.dev/badge/commands/setsunayukiovo/x64dbg-mcp/find-vuln/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/setsunayukiovo/x64dbg-mcp/find-vuln"><img src="https://agentmods.dev/badge/commands/setsunayukiovo/x64dbg-mcp/find-vuln.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 741 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00007	$0.00741
Opus 5.5	$0.00003	$0.00296
Sonnet 5.5	$0.00001	$0.00148
Haiku 4.5	$0.00001	$0.00074

Measured 2mo ago against content hash 1bd329bc2035, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

find-vuln scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/commands/find-vuln.md · 76 lines

How it starts

The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a vulnerability research specialist connected to x64dbg/x32dbg via MCP. Identify potential security vulnerabilities.

If "$1" specifies a type (e.g., "buffer-overflow", "format-string", "use-after-free"), focus on that category. Otherwise, scan broadly.

Phase 1: Target Reconnaissance

Call module_get_main and module_list to understand the binary and dependencies.
Call dump_analyze_module to check security mitigations:
- ASLR (DynamicBase), DEP/NX (NXCompat)
- Stack cookies (__security_check_cookie import)
- SafeSEH / SEHOP, CFG (_guard_check_icall import)
Call module_get_imports on the main module to enumerate all imported APIs — this is the fastest way to see which dangerous APIs the binary uses.
Call function_list filtered to the main module to see recognized functions.

Phase 2: Dangerous API Detection

Search for dangerous APIs using symbol_resolve and symbol_search:

Buffer overflow: strcpy, strcat, sprintf, gets, scanf, lstrcpyA/W, lstrcatA/W
Format string: printf, fprintf, sprintf, wprintf
Memory corruption: memcpy, memmove, RtlCopyMemory (unchecked sizes)
Heap risks: HeapAlloc/HeapFree, malloc/free (double-free, UAF patterns)
Command injection: system, WinExec, ShellExecuteA/W, CreateProcessA/W
Path traversal: CreateFileA/W, DeleteFileA/W with user-controlled paths

Phase 3: Code Pattern Analysis

For each dangerous API found: 5. Call xref_get on the API address to find all call sites in the binary. 6. Call disassembly_at at each call site with count: 30 to see parameter preparation. 7. Check for: size validation before copies, return value checks, fixed-size stack buffers with unbounded operations.

Phase 4: Input Entry Points

Identify input functions: ReadFile, recv, WSARecv, GetWindowTextA/W, GetDlgItemTextA/W, RegQueryValueExA/W.
Trace data flow from input to dangerous APIs.

Phase 5: Report

Read the full file on GitHub · 76 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 76 lines · 7 tokens per session scan A 1bd329bc2035

Subscribe to this mod's changes

find-vuln is a command published in the GitHub repository SetsunaYukiOvO/x64dbg-mcp (554 stars, last pushed 9d ago), licensed MIT. It adds 7 tokens to every session and 741 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.