A read-only analyzer for Windows executable files such as EXE and DLL files. It examines their headers, sections, imported and exported functions, startup callbacks, appended data, and whether an Authenticode code signature is present.

Use it to triage Windows programs, drivers, and native extensions, identify their architecture and type, inspect what system capabilities they request, and collect evidence for deeper analysis.

It provides a quick safety and structure check without loading or running the file. It can highlight signs associated with packing, executable-and-writable memory sections, suspicious imports, and code that runs before the normal entry point.

pe-analyze — Skill for Claude Code and Codex by batteryshark/rekit

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.

Any agent

npx skills add batteryshark/rekit --skill pe-analyze

Clone the repo

git clone --depth 1 https://github.com/batteryshark/rekit

Made for: Claude Code, Codex.

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/skills/batteryshark/rekit/pe-analyze/github.svg)](https://agentmods.dev/skills/batteryshark/rekit/pe-analyze)

Your own site

<a href="https://agentmods.dev/skills/batteryshark/rekit/pe-analyze"><img src="https://agentmods.dev/badge/skills/batteryshark/rekit/pe-analyze/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/skills/batteryshark/rekit/pe-analyze"><img src="https://agentmods.dev/badge/skills/batteryshark/rekit/pe-analyze.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 89 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 525 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.00089	$0.00525
Opus 5.5	$0.00036	$0.00210
Sonnet 5.5	$0.00018	$0.00105
Haiku 4.5	$0.00009	$0.00052

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

Security

Grade A, and why

pe-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 1mo ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/analyze.py, scripts/build.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/pe-analyze/SKILL.md · 50 lines

What it actually says

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 json

Non-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).

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

1mo ago First seen · 50 lines · 89 tokens per session scan A e5186b8dd9d1

Subscribe to this mod's changes

pe-analyze is a skill published in the GitHub repository batteryshark/rekit (20 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 89 tokens to every session and 525 once invoked, about $0.0004 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.

Security

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

component-fixtures

Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.