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.
npx agentmods add skills/batteryshark/rekit/pyinstaller-extractnpx skills add batteryshark/rekit --skill pyinstaller-extractgit clone --depth 1 https://github.com/batteryshark/rekitWrote 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.
[](https://agentmods.dev/skills/batteryshark/rekit/pyinstaller-extract)<a href="https://agentmods.dev/skills/batteryshark/rekit/pyinstaller-extract"><img src="https://agentmods.dev/badge/skills/batteryshark/rekit/pyinstaller-extract.svg" alt="Measured on agentmods" height="20"></a>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.00082 | $0.00522 |
| Opus 5 | $0.00041 | $0.00261 |
| Sonnet 5 | $0.00016 | $0.00104 |
| Haiku 4.5 | $0.00008 | $0.00052 |
Grade A, and why
pyinstaller-extract 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 5d 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.
What it actually says
PyInstaller Extractor
Carve the Python back out of a PyInstaller executable. Pure-stdlib, static,
read-only. The first half of the Python-from-a-binary chain:
pyinstaller-extract → pyc-decompile → py-covert-scan.
When to use
A suspicious standalone executable that's actually a frozen Python app (PyInstaller
is the most common packer for Python malware). This pulls the bundled .pyc modules
out so you can decompile and read them — without running the binary.
What it does
- Finds the PyInstaller CArchive appended to the executable (the
MEIcookie), reads its table of contents, and extracts every entry (modules, data, bundled native libs) to the output dir. - Unpacks the inner PYZ archive into individual
.pycfiles underPYZ-contents/, reconstructing each header from the PYZ's embedded magic so a decompiler can read them. - Reports the target Python version and entry types.
Static: it parses byte structures and marshal.loads the PYZ TOC (that's
deserialization, not execution — code objects are never run). It never launches
the executable or imports any extracted module.
Usage
rekit run pyinstaller-extract ./suspicious.exe ./out
# then decompile the recovered modules:
rekit run pyc-decompile ./out/PYZ-contents/app.pyc ./src
Non-PyInstaller input → {"isPyInstaller": false, "note": "…"}.
Prerequisites
- python3 ≥ 3.8 — pure stdlib, nothing to vendor.
Note
Decompilation of the recovered .pyc is pyc-decompile's job and works best on
CPython 3.7–3.8 targets; newer bytecode extracts fine here but may be out of the
decompiler's range (it will say so).
What ships with it
1 file 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.
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.
- 5d ago First seen · 51 lines · 82 tokens per session scan A 9fc6d97d9a53
pyinstaller-extract is a skill published in the GitHub repository batteryshark/rekit (11 stars, last pushed 26d ago), licensed Apache-2.0. It adds 82 tokens to every session and 522 once invoked, about $0.0004 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…