Pe Analyze
Static triage of Windows PE binaries (EXE/DLL) with pefile: machine/arch, subsystem, entry/imagebase, sections + per-section entropy (packing) and RWX flags, imports classified by capability (inject/exec/network/anti-debug/persist/crypto), exports, TLS callbacks, overlay, and Authenticode presence. Emits BINARY.* atoms. Reads structure only — never runs the binary.
Install
$ agentstack add skill-batteryshark-rekit-pe-analyze ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-batteryshark-rekit-pe-analyze) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
PE Binary Analyzer
Static triage of Windows PE binaries (EXE, DLL, SYS, .node) with pefile.
When to use
You have a Windows binary and want a fast read on what it is and whether it looks malicious — without running it. Pair it with hex-view; its BINARY.* atoms provide structured evidence for downstream analysis.
What it reports
- Header — machine/arch, EXE vs DLL, subsystem, entry point, image base, build
timestamp, Authenticode signature presence (BINARY.NO_SIGNATURE).
- Sections — name, virtual/raw size, Shannon entropy (packing tell →
BINARY.HIGH_ENTROPY), and writable+executable flags (BINARY.RWX_SECTION).
- Imports — DLLs and functions, classified by capability
(inject / exec / network / anti-debug / persist / crypto) → BINARY.SUSPICIOUS_IMPORT.
- Heuristics — high entropy + almost no imports →
BINARY.PACKED; TLS callbacks
(code before entry) → BINARY.TLS_CALLBACK; appended BINARY.OVERLAY.
Strictly static — parses structure via pefile and never loads, maps, or executes the binary. Safe on hostile files.
Usage
rekit run pe-analyze ./sample.exe
rekit run pe-analyze ./driver.sys --format jsonNon-PE input fails honestly ({"ok": false, "error": "not a valid PE: …"}).
Prerequisites
- python3 ≥ 3.8 — pefile is installed under
scripts/site(pure-python), so no
network/install at analysis time.
Rebuilding
scripts/site is populated from the pinned scripts/requirements.txt by scripts/build.sh (uv pip install --target, build time only).
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: batteryshark
- Source: batteryshark/rekit
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.