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 skills add batteryshark/rekit --skill pyc-decompilegit 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/pyc-decompile)<a href="https://agentmods.dev/skills/batteryshark/rekit/pyc-decompile"><img src="https://agentmods.dev/badge/skills/batteryshark/rekit/pyc-decompile/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.
<a href="https://agentmods.dev/skills/batteryshark/rekit/pyc-decompile"><img src="https://agentmods.dev/badge/skills/batteryshark/rekit/pyc-decompile.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00074 | $0.00610 |
| Opus 5.5 | $0.00030 | $0.00244 |
| Sonnet 5.5 | $0.00015 | $0.00122 |
| Haiku 4.5 | $0.00007 | $0.00061 |
Grade A, and why
pyc-decompile 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.
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
Python Bytecode Decompiler
Decompile Python bytecode (.pyc / compiled code objects) back to source with
decompyle3.
When to use
You have compiled Python but not the source: a stray .pyc, the __pycache__ of a
suspicious package, or (most commonly) bytecode carved out of a PyInstaller /
py2exe bundle. Decompiling recovers readable source you can then scan for the real
behaviour.
When inventory finds .pyc artifacts with no matching source, decompile them and
rescan the recovered .py.
What it does
Reads the bytecode statically (unmarshals the code object, disassembles it) and
reconstructs equivalent Python source. It does not import, exec, or run the
.pyc — safe on hostile bytecode.
Best on CPython 3.7–3.8 bytecode (decompyle3's target range). The runner detects
the bytecode's version and tells you whether it's in range; for older bytecode use
uncompyle6, and 3.9+ needs a version-matched decompiler.
Usage
rekit run pyc-decompile ./payload.pyc ./out
# or
python3 skills/pyc-decompile/scripts/run.py ./payload.pyc ./out
Writes out/decompiled.py and prints a JSON result:
{"ok": true, "outputFile": "out/decompiled.py", "detectedVersion": "3.8",
"supported": true, "bytesOut": 412}
On an out-of-range or corrupt .pyc it fails honestly with the detected version and
a pointer to the right tool — it does not emit a half-guessed decompilation.
Prerequisites
- python3 ≥ 3.8 — to run the decompiler. The target
.pycmay be a different version; decompyle3 (and its pure-Python deps) is installed underscripts/site, so no network/install at analysis time.
Rebuilding the payload
scripts/site is populated from a pinned scripts/requirements.txt by
scripts/build.sh (uv pip install --target, build time only). Pure-Python, so the
vendored tree is portable across OS/arch.
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.
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 · 60 lines · 74 tokens per session scan A 25176150de8b
pyc-decompile is a skill published in the GitHub repository batteryshark/rekit (20 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 74 tokens to every session and 610 once invoked, about $0.0003 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.
Other skills, from other repositories
matlab
Builds, reviews, migrates, and plans MATLAB or GNU Octave numerical workflows. Use for arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
pennylane
Builds and differentiates PennyLane quantum circuits, hybrid PyTorch or JAX models, molecular VQE and QAOA workflows. Use for variational quantum algorithms, quantum machine learning, simulator validation, and moving validated circuits to provider plugins. For hardware-specific compilation use qiskit or cirq; for…
holoscan-install-wheel
Install Holoscan SDK 5.x CUDA 13 Python wheels in an isolated environment, choosing the full stack or version-matched components.
rocm-kernels
Provides guidance for writing and benchmarking optimized Triton kernels for AMD GPUs (MI355X, R9700) on ROCm, targeting HuggingFace diffusers (LTX-Video, SD3, FLUX) and transformers. Core kernels: RMSNorm, RoPE 3D, GEGLU, AdaLN. Includes XCD swizzle, autotune, diffusers integration patterns, and LTX-Video pipeline…
typing-exclusion-worker
Python typing exclusion worker: remove assigned mypy exclusion modules in small scoped batches, fix typing issues, run validation, and produce a structured completion summary. Use when running parallel typing-debt workers or when asked to remove modules from pyproject mypy exclusion overrides.
python
Python development with ruff, mypy, pytest - TDD and type safety.