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/cyberkaida/reverse-engineering-assistant/pyghidra-scriptingnpx 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.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.00209 | $0.04177 |
| Opus 5 | $0.00105 | $0.02089 |
| Sonnet 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 4d 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.
- 4d 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 (822 stars, last pushed yesterday), licensed Apache-2.0. It adds 209 tokens to every session and 4,177 once invoked, about $0.0010 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
analyzing-golang-malware-with-ghidra
Reverse engineer Go-compiled malware in Ghidra by parsing Go buildinfo and pclntab structures, recovering stripped/obfuscated function names (e.g. via GoResolver), and extracting embedded module/dependency strings and types from Go binaries. Use when analyzing a Go-language malware sample, deobfuscating a…
gmail-email
Send emails via Gmail SMTP using App Password authentication.
example-skill
Example skill that demonstrates the gitagent skills system. Use this to test skill loading and script execution.
analyzing-golang-malware-with-ghidra
Reverse engineer Go-compiled malware using Ghidra with specialized scripts for function recovery, string extraction, and type reconstruction in stripped Go binaries.
osgrep-reference
Comprehensive CLI reference and search strategies for osgrep semantic code search. Use for detailed CLI options, index management commands, search strategy guidance (architectural vs targeted queries), and troubleshooting. Complements the osgrep plugin which handles daemon lifecycle.
mem0-api
Complete reference for building applications with the Mem0 memory API and SDK — a persistent, self-improving memory layer for LLM agents and chatbots. ALWAYS use this skill when the user mentions: "mem0", "mem0ai", "MemoryClient", "Memory()", "memory layer for AI", "persistent agent memory", "long-term memory for…