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 cyberkaida/reverse-engineering-assistant --skill pyghidra-scriptinggit clone --depth 1 https://github.com/cyberkaida/reverse-engineering-assistantWrote 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/cyberkaida/reverse-engineering-assistant/pyghidra-scripting)<a href="https://agentmods.dev/skills/cyberkaida/reverse-engineering-assistant/pyghidra-scripting"><img src="https://agentmods.dev/badge/skills/cyberkaida/reverse-engineering-assistant/pyghidra-scripting/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/cyberkaida/reverse-engineering-assistant/pyghidra-scripting"><img src="https://agentmods.dev/badge/skills/cyberkaida/reverse-engineering-assistant/pyghidra-scripting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00209 | $0.04177 |
| Opus 5.5 | $0.00084 | $0.01671 |
| Sonnet 5.5 | $0.00042 | $0.00835 |
| Haiku 4.5 | $0.00021 | $0.00418 |
Grade A, and why
pyghidra-scripting 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.
How it starts
The opening of the file, as written. The whole thing — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PyGhidra scripting via ReVa
ReVa exposes five MCP tools under the scripts provider that let an assistant write, edit, run, and inspect Python scripts inside the same Ghidra session ReVa is serving. The Python code runs under PyGhidra (CPython 3 + JPype), so it has the full Ghidra Java API available — the FlatProgramAPI, DecompInterface, FunctionManager, everything.
This skill teaches when to reach for these tools, how to structure the Python you send to run-script, and the pitfalls that bite in practice.
The five tools at a glance
| Tool | Purpose | Use when |
|---|---|---|
run-script |
Execute Python against a program. Inline code, or by scriptPath / scriptName. |
The dedicated ReVa MCP tools don't cover what you need, or you want one tight pass over the program. |
list-scripts |
Enumerate scripts across registered directories. Filterable by name/path; paginated. | Discovering what's already saved before writing a new one. |
read-script |
cat -n view of a script with offset / limit and a truncated flag. |
Reading an existing script before editing it. The numbered output is what edit-script lines up against. |
write-script |
Create a new .py file (or full overwrite with overwrite: true). User-writeable dirs only. |
Saving a reusable script. Never reach for this just to bundle inline code — use run-script with code for one-shot use. |
edit-script |
old_string → new_string replacement. Errors if old_string matches multiple places unless replace_all: true. |
Iterating on an existing script. Pair with read-script to see line context first. |
Reach-for-it triggers
run-script is the escape hatch. Use it when:
- You need to run a custom predicate over every function/symbol/instruction and the existing list/find tools don't filter the right way.
- You need to combine multiple Ghidra API calls into one operation that would otherwise take many MCP round-trips.
- You want to use a Ghidra API ReVa doesn't expose — e.g.
DecompInterfacelow-level features,PCodeanalysis, customAddressSetarithmetic, the data flow API directly,BinaryReader, etc. - You're prototyping; once it works and is reusable, save it with
write-script.
What ships with it
5 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 · 241 lines · 209 tokens per session scan A a35e374ccf93
pyghidra-scripting is a skill published in the GitHub repository cyberkaida/reverse-engineering-assistant (879 stars, last pushed today), licensed Apache-2.0. It adds 209 tokens to every session and 4,177 once invoked, about $0.0008 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
idapython
IDA Pro Python scripting for reverse engineering. Use when writing IDAPython scripts, analyzing binaries, working with IDA's API for disassembly, decompilation (Hex-Rays), type systems, cross-references, functions, segments, or any IDA database manipulation. Covers ida modules (50+), idautils iterators, and common…
stack-trace-python-probe
Internal helper for meta-stack-trace-investigator. Use when a Python traceback needs Python-specific root-cause checks, pytest reproducer guidance, and defensive patch targets.
python-debugpy
Debug Python with pdb, breakpoint(), post-mortem inspection, and debugpy remote or headless attach.
bugfix-protocol
Protocolo sistemático de depuración en 6 fases. Enfoque estructurado ante errores con verificaciones rápidas, pruebas aisladas, regla de los 20 minutos y plantilla de informe de errores.
bugfix-protocol
A six-stage debugging process covering quick checks, diagnosis, isolated reproduction, a small fix, verification, and documentation. It also includes a rule to change approach or ask for help after 20 minutes without progress.
bugfix-protocol
Systematic 6-phase debugging protocol. Structured approach to bugs with quick checks, isolated testing, 20-minute rule, and bug report template.