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 automating-analysis-with-r2pipegit 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/automating-analysis-with-r2pipe)<a href="https://agentmods.dev/skills/meltedinhex/analyst-ai-pack/automating-analysis-with-r2pipe"><img src="https://agentmods.dev/badge/skills/meltedinhex/analyst-ai-pack/automating-analysis-with-r2pipe/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/automating-analysis-with-r2pipe"><img src="https://agentmods.dev/badge/skills/meltedinhex/analyst-ai-pack/automating-analysis-with-r2pipe.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.00069 | $0.00689 |
| Opus 5 | $0.00034 | $0.00345 |
| Sonnet 5 | $0.00014 | $0.00138 |
| Haiku 4.5 | $0.00007 | $0.00069 |
Grade A, and why
automating-analysis-with-r2pipe 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 10d 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
Automating Analysis With r2pipe
When to Use
- You want to script radare2/rizin to extract functions, imports, strings, and cross-references programmatically, across one or many samples.
- You are building a repeatable triage pipeline on top of r2's analysis commands.
Do not use r2 to debug/run the sample here — this skill drives static analysis commands
(aaa, aflj, izj, iij). Run inside an isolated environment.
Prerequisites
- radare2 (or rizin) installed and the
r2pipePython package (the script degrades gracefully and reports unavailability if absent).
Safety & Handling
- r2 static analysis does not execute the sample; keep the working directory isolated.
Workflow
Step 1: Confirm r2pipe availability
python scripts/analyst.py check
Reports whether r2pipe and an r2/rizin binary are available.
Step 2: Extract an analysis summary
python scripts/analyst.py summary sample.bin
Opens the binary, runs analysis (aaa), and collects functions (aflj), imports (iij), and
strings (izj) as structured JSON.
Step 3: Query cross-references
For a function of interest, gather xrefs to/from to map call relationships.
Step 4: Aggregate
Combine per-sample summaries for comparison and signature development.
Validation
- The summary returns non-empty functions/imports for a normal binary.
- JSON commands (
*j) are parsed, not screen-scraped text. - Missing r2pipe/r2 is reported clearly rather than crashing.
Pitfalls
- Forgetting to run
aaabefore querying functions (empty results). - Mixing radare2 and rizin command differences in scripted output.
- Very large binaries making
aaaslow — scope analysis as needed.
References
- See
references/api-reference.mdfor the automation wrapper. - r2pipe and radare2 command references (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.
- 10d ago First seen · 93 lines · 69 tokens per session scan A 81bdcaca58a5
automating-analysis-with-r2pipe is a skill published in the GitHub repository meltedinhex/analyst-ai-pack (22 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 69 tokens to every session and 689 once invoked, about $0.0003 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-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 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.
reverse-engineering-workbench
Coordinate EVOKORE reverse-engineering work across Ghidra-style static analysis, semantic recovery, and debugger-guided triage. Use when opening an unfamiliar binary, planning a decompilation workflow, or choosing between static and dynamic analysis paths.