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 reverse-engineering-binaries-with-radare2-rizingit 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/reverse-engineering-binaries-with-radare2-rizin)<a href="https://agentmods.dev/skills/meltedinhex/analyst-ai-pack/reverse-engineering-binaries-with-radare2-rizin"><img src="https://agentmods.dev/badge/skills/meltedinhex/analyst-ai-pack/reverse-engineering-binaries-with-radare2-rizin/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/reverse-engineering-binaries-with-radare2-rizin"><img src="https://agentmods.dev/badge/skills/meltedinhex/analyst-ai-pack/reverse-engineering-binaries-with-radare2-rizin.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.00078 | $0.00700 |
| Opus 5 | $0.00039 | $0.00350 |
| Sonnet 5 | $0.00016 | $0.00140 |
| Haiku 4.5 | $0.00008 | $0.00070 |
Grade A, and why
reverse-engineering-binaries-with-radare2-rizin 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 8d 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
Reverse Engineering Binaries With radare2/rizin
When to Use
- You want to statically reverse a binary with the radare2/rizin command set: analyze, navigate functions, read disassembly/graphs, and patch.
- You prefer a scriptable, terminal-based RE workflow.
Do not use r2's debug mode (-d) to run untrusted samples on your host — for static RE, open
without debugging. Work in an isolated environment.
Prerequisites
- radare2 or rizin installed and the sample (read inertly).
Safety & Handling
- Static analysis does not execute the sample; keep the working directory isolated.
Workflow
Step 1: Open and analyze
python scripts/analyst.py cheatsheet analyze
Prints the core sequence: open read-only (r2 -e bin.cache=true sample), aaa to analyze, afl
to list functions, iI/ie for info/entrypoint.
Step 2: Navigate and disassemble
Use s <addr>/s main to seek, pdf to print a function, VV for the graph view, and axt for
cross-references.
Step 3: Annotate
Rename with afn, add comments with CC, define data with Cd, and flag locations with f.
Step 4: Patch (optional)
In write mode (-w), use wa/wx to assemble/patch and re-verify with pdf.
Validation
aaacompletes andafllists functions before deeper navigation.- Commands used are real r2/rizin commands (verifiable in the book).
- Patches are re-disassembled to confirm the intended change.
Pitfalls
- Forgetting
aaa, leaving functions undefined. - Confusing radare2 and rizin command differences in scripts.
- Opening with
-d(debug/run) when only static analysis is intended.
References
- See
references/api-reference.mdfor the command cheatsheet tool. - The radare2 book and Rizin 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.
- 8d ago First seen · 89 lines · 78 tokens per session scan A dda33f10279e
reverse-engineering-binaries-with-radare2-rizin is a skill published in the GitHub repository meltedinhex/analyst-ai-pack (22 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 78 tokens to every session and 700 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. 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-malicious-pdf-with-peepdf
A Chinese-language skill for examining suspicious PDF files with peepdf, pdfid, and pdf-parser. It is intended for static malware analysis, which studies a file without running it.
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-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-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.