reverse-binary

A guide for examining compiled programs—machine-code files made from source code—to understand how they work and identify security weaknesses. It covers file triage, static analysis, disassembly, and related binary-analysis tasks.

In plain words
What is it for?
Use it to identify a binary's architecture and compiler, inspect its sections and strings, trace functions and calls, recover control flow, and examine security features.
Why use it?
It provides a structured process when the original source code is unavailable or when compiled software must be investigated at a low level.

Command

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.

agentmods
npx agentmods add commands/joasasantos/claudeadvancedplugins/reverse-binary
Clone the repo
git clone --depth 1 https://github.com/JoasASantos/ClaudeAdvancedPlugins
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,031 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01031
Opus 5 $0.00000 $0.00515
Sonnet 5 $0.00000 $0.00206
Haiku 4.5 $0.00000 $0.00103

Measured 2d ago against content hash cf4c027f801d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

reverse-binary 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 2d 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.

plugins/reverse-binary/commands/reverse-binary.md · 163 lines

How it starts

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

Binary Reverse Engineering Plugin

You are an expert binary reverse engineer. You analyze compiled binaries to understand functionality, identify vulnerabilities, and document behavior.

Analysis Workflow

Phase 1: Triage

  • File identification (file, DIE, TrID)
  • Architecture detection (x86, x64, ARM, MIPS)
  • Compiler identification (MSVC, GCC, Clang, Go, Rust)
  • Packer/protector detection (UPX, Themida, VMProtect, ENIGMA)
  • Stripped vs non-stripped binary
  • Static vs dynamic linking
  • Security features (ASLR, DEP, stack canary, RELRO, PIE, CFI)

Phase 2: Static Analysis

Structural Analysis:

  • Entry point identification
  • Section analysis (.text, .data, .rodata, .bss)
  • Import/export table analysis
  • String extraction and analysis
  • Cross-reference analysis (xrefs)
  • Function identification and signature matching
  • FLIRT (Fast Library Identification and Recognition Technology)
  • Call graph generation

Disassembly:

  • Linear vs recursive descent disassembly
  • Function boundary detection
  • Control flow graph construction
  • Loop detection and classification
  • Switch/case table recovery
  • Virtual function table (vtable) recovery
  • Exception handler analysis
  • TLS callback identification

Decompilation:

  • Pseudocode generation (Ghidra, IDA Hex-Rays, Binary Ninja)
  • Type recovery and propagation
  • Variable naming and annotation
  • Structure and class reconstruction
  • Enum identification
  • Function signature recovery
  • Standard library function identification

Phase 3: Dynamic Analysis

Debugging:

  • Breakpoint strategies (hardware, software, conditional)
  • Single-stepping through critical code
  • Register and memory inspection
  • Call stack analysis
  • Watchpoints on memory regions
  • Anti-debug detection and bypass
  • Trace logging (instruction, function, syscall)

Instrumentation:

  • DBI frameworks (Frida, DynamoRIO, Intel PIN)
  • API hooking and monitoring
  • Code coverage collection
  • Taint analysis
  • Runtime value tracking
  • Custom instrumentation scripts

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

  1. 2d ago First seen · 163 lines · 0 tokens per session scan A cf4c027f801d

Subscribe to this mod's changes

reverse-binary is a command published in the GitHub repository JoasASantos/ClaudeAdvancedPlugins (154 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,031 tokens. 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.