What is hunt-strings?

A command for searching text inside a running Windows program or library, including strings stored in ordinary and wide-character formats. It also checks where each matching string is referenced in the program.

Use it during binary analysis to search for a supplied text pattern or scan for high-value categories. It reads surrounding memory and identifies references to interesting strings.

It helps locate clues such as URLs, file paths, error messages, credentials, registry keys, and cryptography-related text in a binary. Cross-references show which code areas use each match.

hunt-strings — Command for Claude Code by SetsunaYukiOvO

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 skills, 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/hunt-strings/github.svg)](https://agentmods.dev/commands/setsunayukiovo/x64dbg-mcp/hunt-strings)

Your own site

<a href="https://agentmods.dev/commands/setsunayukiovo/x64dbg-mcp/hunt-strings"><img src="https://agentmods.dev/badge/commands/setsunayukiovo/x64dbg-mcp/hunt-strings/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/hunt-strings"><img src="https://agentmods.dev/badge/commands/setsunayukiovo/x64dbg-mcp/hunt-strings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 613 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.00006	$0.00613
Opus 5	$0.00003	$0.00307
Sonnet 5	$0.00001	$0.00123
Haiku 4.5	$0.00001	$0.00061

Measured 11d ago against content hash 31bb5f4eb198, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

hunt-strings 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 11d 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/hunt-strings.md · 72 lines

How it starts

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

You are a string analysis specialist connected to x64dbg/x32dbg via MCP. Search for interesting strings in the binary.

Phase 1: Context

Call module_get_main to identify the target.
Call module_list for all loaded modules and address ranges.
Call dump_analyze_module to understand section layout (.rdata, .data, .rsrc).

Phase 2: Search

If "$1" is provided, search for that specific pattern: 4. Call memory_search with "$1" as pattern in the main module range.

Also search for UTF-16LE encoding (wide strings).

For each match, call memory_read at the address with size: 256 for full context.

If "$1" is empty, search for high-value categories: 4. Search using memory_search for:

Credentials: password, secret, token, api_key, auth
Network: http://, https://, ftp://, .com, .net
File paths: C:, .exe, .dll, .dat, .cfg, .ini
Debug/Error: error, fail, debug, assert, exception
Registry: HKEY_, SOFTWARE, CurrentVersion
Crypto: AES, RSA, SHA, MD5, encrypt, decrypt

Phase 3: Cross-Reference Analysis

For each interesting string found: 6. Note the string address. 7. Call xref_get on the string address to find direct references from code. 8. If xref_get returns no results, fall back to memory_search for the address bytes (little-endian) in code sections. 9. For each cross-reference, call disassembly_at with count: 15 to see how the string is used. 10. Call symbol_from_address to identify the referencing function. 11. Call function_get at the referencing address to see the full function context.

Phase 4: Report

=== String Analysis Report ===

Target: [binary name]
Search: [pattern or "comprehensive scan"]

=== High Priority ===

[CREDENTIAL] @ 0x...
  String: "..."
  Referenced by: 0x... ([function])
  Context: [how it's used]

[NETWORK] @ 0x...
  String: "https://..."
  Referenced by: 0x... ([function])

=== By Category ===

Credentials: [count]
URLs: [count]
File Paths: [count]
Debug Messages: [count]
Registry Keys: [count]

=== Recommendations ===
  1. [strings warranting deeper investigation]
  2. [breakpoints to set]
  3. [security concerns]

Read the full file on GitHub · 72 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.

11d ago First seen · 72 lines · 6 tokens per session scan A 31bb5f4eb198

Subscribe to this mod's changes

hunt-strings is a command published in the GitHub repository SetsunaYukiOvO/x64dbg-mcp (460 stars, last pushed 20d ago), licensed MIT. It adds 6 tokens to every session and 613 once invoked, about $0.0000 per session on Opus 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.

Debugging

qa-changes

This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…

OpenHands/extensions · 63 tokens

doctor

Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…

doncheli/don-cheli-sdd · 76 tokens

hunt-strings

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Phase 1: Context

Phase 2: Search

Phase 3: Cross-Reference Analysis

Phase 4: Report

What this file has done since we first saw it

Other commands, from other repositories

qa-changes

doctor

fix

doctor

http-service

gh-issue-use-cypress