A command for examining Windows PE files, the executable format used by many Windows programs, through their headers, text, machine code, and structure.

Use it in reverse engineering or malware analysis to identify the file, calculate its hash, inspect imports and exports, examine sections, extract strings, disassemble code, and classify the binary.

It gathers the main evidence needed to understand an unknown program without running it.

analyze — Command by ogrodev

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/ogrodev/fsociety/analyze

Clone the repo

git clone --depth 1 https://github.com/ogrodev/fsociety

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

When invoked 909 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.

Model	Per session	Once invoked
Fable 5	$0.00014	$0.00909
Opus 5	$0.00007	$0.00454
Sonnet 5	$0.00003	$0.00182
Haiku 4.5	$0.00001	$0.00091

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

Security

Grade A, and why

analyze 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.

romero/commands/analyze.md · 109 lines

How it starts

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

Storage Policy: ALL output files MUST be saved in the project directory. NEVER write to /tmp/ or any system temporary directory.

Full Binary Analysis

Parse $ARGUMENTS to get the binary path. This command runs the complete 8-phase reverse engineering workflow.

Pre-flight

Verify the binary exists at the provided path.

Check tool availability:

node "${CLAUDE_PLUGIN_ROOT}/scripts/tool-checker.js" check

If critical Tier 1 tools are missing, inform the user and suggest /re-install.

Phase 1 — Initial Assessment

Compute hashes:

node "${CLAUDE_PLUGIN_ROOT}/scripts/binary-hasher.js" hash "$ARGUMENTS"

Check for prior analysis:

node "${CLAUDE_PLUGIN_ROOT}/scripts/analysis-tracker.js" check "<sha256>" "full-analysis"

File type identification: file <binary>
Record basic metadata: size, timestamps.

Phase 2 — PE Structure Analysis

Use radare2 for PE header analysis:

r2 -qc 'iH' <binary>     # PE headers
r2 -qc 'iI' <binary>     # Binary info
r2 -qc 'iS' <binary>     # Sections (check entropy)
r2 -qc 'ii' <binary>     # Imports
r2 -qc 'iE' <binary>     # Exports
r2 -qc 'ir' <binary>     # Resources

Flag suspicious indicators:

High-entropy sections (>7.0 = likely packed)
Unusual section names (.UPX, .aspack, .nsp)
Suspicious imports (CreateRemoteThread, VirtualAllocEx, WSAStartup)
TLS callbacks (anti-debug)

Phase 3 — String & Secret Extraction

strings -a -n 6 <binary>              # ASCII strings
strings -a -n 6 -el <binary>          # UTF-16 LE strings
floss <binary>                          # Obfuscated/stack strings

Regex-match for: URLs, IPs, emails, API keys (AWS AKIA*, Azure, GCP AIza*), JWT tokens (eyJ*), base64 blobs, file paths, registry keys, wallet addresses.

Log each finding:

node "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" add "<binary>" "<type>" "<value>" "<severity>" "<title>"

Phase 4 — Disassembly & Function Analysis

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

2d ago First seen · 109 lines · 14 tokens per session scan A 0d3d6f8f930b

Subscribe to this mod's changes

analyze is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 909 once invoked, about $0.0001 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.

Productivity Security claude-code claude-code-plugin offensive-security pentesting

pr

Create a PR to main branch using conventional commit style for the title.

KeygraphHQ/shannon · 13 tokens

engage.scope

Execute Phase 0 - Scope Definition and Rules of Engagement.

hypnguyen1209/offensive-claude · 11 tokens

pentest

Activate pentest mode — displays ASCII art, configures session isolation, collects engagement scope, then OWNS the engagement: pre-flight, recon, planning (via the pentester-orchestrator planner), executor dispatch, a time-budget quota loop, aggregation, and report generation.

Stickman230/claude-pentest · 58 tokens

analyze