A command for identifying software packers, which compress or protect executable files, and attempting to unpack them.

Use it to inspect a binary, check its sections and entropy, unpack UPX-protected files, or document next steps for other packers.

Packed binaries can hide their code and make analysis difficult; this command helps identify the protection and produces an unpacked copy when UPX is used.

unpack — 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/unpack

Clone the repo

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

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 641 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.00007	$0.00641
Opus 5	$0.00003	$0.00320
Sonnet 5	$0.00001	$0.00128
Haiku 4.5	$0.00001	$0.00064

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

Security

Grade A, and why

unpack 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/unpack.md · 83 lines

How it starts

The opening of the file, as written. The whole thing — 83 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.

Packer Detection & Unpacking

Parse $ARGUMENTS to get the binary path.

Step 1 — Identify Packing

Entropy analysis:
```
r2 -qc 'iS' <binary>
```
Sections with entropy > 7.0 are likely packed.
File identification:
```
file <binary>
```
Known packer signatures:
- UPX: UPX0, UPX1 sections, or UPX! magic at offset
- ASPack: .aspack, .adata sections
- Themida/WinLicense: .winlicense, .themida sections
- VMProtect: .vmp0, .vmp1 sections
- Enigma: .enigma section
- .NET Reactor: .reacto section
- Confuser: Garbled section names in .NET

Step 2 — Attempt Unpacking

If UPX detected:

mkdir -p extracted
upx -d <binary> -o extracted/unpacked-<binary-name>

Verify the unpacked file:

file extracted/unpacked-<binary-name>
r2 -qc 'iS' extracted/unpacked-<binary-name>

If other packer: Document the packer type and suggest manual approaches:

ASPack: Try generic unpackers or dump from memory
Themida/VMProtect: Requires dynamic unpacking (run under debugger, dump at OEP)
.NET obfuscation: Use /dotnet with de4dot
Custom packer: Use Frida for runtime memory dumping

Ask the user which approach to take:

AskUserQuestion: The binary is packed with <packer>. Options:
1. Attempt automated unpacking
2. Dynamic memory dump (requires wine + frida)
3. Skip unpacking, analyze packed binary
4. Manual approach (provide guidance)

Step 3 — Verify Unpacked Binary

Check that the unpacked file is a valid PE:
```
file extracted/unpacked-<binary-name>
```

Compare entropy before/after:

r2 -qc 'iS' extracted/unpacked-<binary-name>

Verify imports are now visible:

r2 -qc 'ii' extracted/unpacked-<binary-name>

Step 4 — Re-analyze

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

Subscribe to this mod's changes

unpack is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 5mo ago), licensed MIT. It adds 7 tokens to every session and 641 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.

Documents 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

unpack