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 meltedinhex/analyst-ai-pack --skill scripting-ghidra-headless-analysisgit clone --depth 1 https://github.com/meltedinhex/analyst-ai-packWrote 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/meltedinhex/analyst-ai-pack/scripting-ghidra-headless-analysis)<a href="https://agentmods.dev/skills/meltedinhex/analyst-ai-pack/scripting-ghidra-headless-analysis"><img src="https://agentmods.dev/badge/skills/meltedinhex/analyst-ai-pack/scripting-ghidra-headless-analysis/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/meltedinhex/analyst-ai-pack/scripting-ghidra-headless-analysis"><img src="https://agentmods.dev/badge/skills/meltedinhex/analyst-ai-pack/scripting-ghidra-headless-analysis.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.00079 | $0.00738 |
| Opus 5 | $0.00039 | $0.00369 |
| Sonnet 5 | $0.00016 | $0.00148 |
| Haiku 4.5 | $0.00008 | $0.00074 |
Grade A, and why
scripting-ghidra-headless-analysis 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 9d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scripting Ghidra Headless Analysis
When to Use
- You need to auto-analyze many samples (or re-run a consistent analysis) without the Ghidra GUI.
- You want to generate the
analyzeHeadlesscommand and a post-script that exports functions, strings, or decompiled output.
Do not use this to run untrusted samples — Ghidra analyzes binaries statically and never executes them, but keep the import directory isolated. This skill prepares automation, it does not run the binary.
Prerequisites
- A Ghidra installation (
analyzeHeadlessinsupport/) and the samples to import.
Safety & Handling
- Ghidra does not execute the sample; still store imports in an isolated, defanged directory.
Workflow
Step 1: Generate the headless command
python scripts/analyst.py command --project /proj --name Batch --import ./samples --script export.py
Builds an analyzeHeadless invocation with project path, import directory, post-script, and common
flags (-recursive, -overwrite, -deleteProject optional).
Step 2: Generate a post-analysis script skeleton
python scripts/analyst.py postscript --out export.py --emit functions,strings
Emits a Ghidra Python (Jython) script that iterates functions/strings and writes JSON next to the program.
Step 3: Run and collect
Execute the generated command, then aggregate the per-sample JSON exports.
Step 4: Review
Spot-check a few exports to confirm analysis completeness before scaling up.
Validation
- The generated command references a valid project path, import dir, and existing post-script.
- The post-script uses real Ghidra API calls (
currentProgram,getFunctionManager). - Output JSON is produced per imported program.
Pitfalls
- Forgetting
-overwrite/-recursive, causing skipped or duplicate imports. - Jython 2 syntax constraints in post-scripts (no f-strings).
- Project lock conflicts when running multiple headless jobs on one project.
References
- See
references/api-reference.mdfor the generator. - Ghidra analyzeHeadless and API docs (linked in frontmatter).
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.
- 9d ago First seen · 94 lines · 79 tokens per session scan A 40f24d3a21ca
scripting-ghidra-headless-analysis is a skill published in the GitHub repository meltedinhex/analyst-ai-pack (22 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 79 tokens to every session and 738 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-09-03.
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…
analyzing-malicious-pdf-with-peepdf
Perform static analysis of malicious PDF documents using peepdf, pdfid, and pdf-parser to extract embedded JavaScript, shellcode, and suspicious objects.
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.
analyzing-malicious-pdf-with-peepdf
Perform static analysis of malicious PDF documents using peepdf, pdfid, and pdf-parser to extract embedded JavaScript, shellcode, and suspicious objects. Use when triaging a suspicious PDF attachment from a phishing email, analyzing a PDF-based exploit document, or building detection signatures for weaponized PDF…
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.
analyzing-golang-malware-with-ghidra
A malware-analysis workflow for examining Go programs with Ghidra, a reverse-engineering tool, including stripped or obfuscated compiled files.