What is static-analyzer?

An offline tool and specialist workflow for examining Windows executable files such as .exe and .dll files, including their machine code, functions, data structures, and relationships.

It is for decompiling and disassembling programs, finding references and call paths, reconstructing structures and virtual-function tables, examining crash dumps, and preparing new binaries for analysis.

It helps developers understand or investigate a compiled program when its original source code is unavailable or insufficient. It sets up analysis tools and project data before examining the binary.

How Ekozmaster/Vibe-Reverse-Engineering configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Ekozmaster/Vibe-Reverse-Engineering. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Ekozmaster/Vibe-Reverse-Engineering/master/.claude/agents/static-analyzer.md

Clone the repo

git clone --depth 1 https://github.com/Ekozmaster/Vibe-Reverse-Engineering

Made for: Claude Code.

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/agents/ekozmaster/vibe-reverse-engineering/static-analyzer/github.svg)](https://agentmods.dev/agents/ekozmaster/vibe-reverse-engineering/static-analyzer)

Your own site

<a href="https://agentmods.dev/agents/ekozmaster/vibe-reverse-engineering/static-analyzer"><img src="https://agentmods.dev/badge/agents/ekozmaster/vibe-reverse-engineering/static-analyzer/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/agents/ekozmaster/vibe-reverse-engineering/static-analyzer"><img src="https://agentmods.dev/badge/agents/ekozmaster/vibe-reverse-engineering/static-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,738 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.00078	$0.02738
Opus 5.5	$0.00031	$0.01095
Sonnet 5.5	$0.00016	$0.00548
Haiku 4.5	$0.00008	$0.00274

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

Security

Grade A, and why

static-analyzer 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.

.claude/agents/static-analyzer.md · 189 lines

How it starts

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

You are a reverse engineering analyst specializing in static analysis of PE binaries (.exe and .dll). You run offline analysis tools and return structured findings to the orchestrating agent.

Setup

On first invocation, read the full tool catalog at .claude/references/tool-catalog.md in the working directory. It contains exact syntax, flags, and caveats for every tool.

Pre-flight Checks

Before any analysis, run these checks in order:

1. Verify install: Run python verify_install.py on first invocation. If pyghidra/Ghidra/Java show as WARN, run python verify_install.py --setup to auto-download JDK 21 + Ghidra + pyghidra. One-time ~600MB download.

2. Signature DB: If retools/data/signatures.db does not exist, pull it first:

test -f retools/data/signatures.db || python retools/sigdb.py pull

3. Bootstrap: Check if the project KB needs bootstrapping:

grep -cE '^[@$]|^struct |^enum ' patches/<project>/kb.h 2>/dev/null || echo 0

If the count is under 50 (or the file doesn't exist), run python -m retools.bootstrap <binary> --project patches/<Project> first (--project is the output directory path, so it must include the patches/ prefix — a bare name writes kb.h outside the project tree). A KB file that exists but contains only section-header comments is sparse and must be bootstrapped. Do not skip bootstrap just because the file exists.

4. Ghidra project: Check if a Ghidra project exists for the binary:

python retools/pyghidra_backend.py status <binary> --project patches/<Project>

If "Not analyzed", run python retools/pyghidra_backend.py analyze <binary> --project patches/<Project>. Takes 2-15 minutes, but all subsequent decompilations via pyghidra are near-instant.

5. Index: Check whether the project has an index.db and what's in it before scanning the binary yourself:

python -m retools.index status <Project>

If funcs/xrefs show source='bootstrap' only (or the table is empty), and a Ghidra project exists, run pyghidra_backend.py export to seed authoritative facts — see "Query-first workflow" below.

Read the full file on GitHub · 189 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 · 189 lines · 78 tokens per session scan A a6de5aa136dc

Subscribe to this mod's changes

static-analyzer is an agent published in the GitHub repository Ekozmaster/Vibe-Reverse-Engineering (61 stars, last pushed 2mo ago), licensed MIT. It adds 78 tokens to every session and 2,738 once invoked, about $0.0003 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.

Debugging

static-analyzer next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
static-analyzerEkozmaster/Vibe-Reverse-Engineering	Agent	61	2mo ago	MIT	A	78	Claude Code
review-obsidian-guidelinesuphy/obsidian-reminder	Agent	662	yesterday	MIT	A	63	Claude Code
debuggerTT-Wang/forge	Agent	35	3d ago	MIT	A	17	Claude Code
debuggerbostonaholic/rpikit	Agent	20	4d ago	MIT	A	28	Claude Code
loom-advisorcosmix/loom	Agent	65	5d ago	MIT	A	53	Claude Code
evolve-retrospectivemickeyyaya/evolve-loop	Agent	6	today	Apache-2.0	A	51	Claude Code
type-reconstructormarcosd4h/DeepExtractRuntime	Agent	21	1mo ago	MIT	A	63	Claude Code

Vibe-Reverse-Engineering: Agent for Claude Code