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 setting-up-an-isolated-malware-analysis-labgit 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/setting-up-an-isolated-malware-analysis-lab)<a href="https://agentmods.dev/skills/meltedinhex/analyst-ai-pack/setting-up-an-isolated-malware-analysis-lab"><img src="https://agentmods.dev/badge/skills/meltedinhex/analyst-ai-pack/setting-up-an-isolated-malware-analysis-lab/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/setting-up-an-isolated-malware-analysis-lab"><img src="https://agentmods.dev/badge/skills/meltedinhex/analyst-ai-pack/setting-up-an-isolated-malware-analysis-lab.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.00060 | $0.01247 |
| Opus 5 | $0.00030 | $0.00624 |
| Sonnet 5 | $0.00012 | $0.00249 |
| Haiku 4.5 | $0.00006 | $0.00125 |
Grade A, and why
setting-up-an-isolated-malware-analysis-lab scanned grade A with 1 finding 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.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo nano /etc/inetsim/inetsim.conf # set service_bind_address and dns_default_ip Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setting Up an Isolated Malware Analysis Lab
When to Use
- You need to run unknown or known-malicious binaries to observe behavior without risk to production systems or the internet.
- You are standing up a repeatable analysis environment for static and dynamic work.
- You want a reverting, snapshot-based workflow so each sample starts from a clean state.
Do not use this as guidance for detonating samples on a host OS or a cloud VM with live egress; that risks self-spreading malware escaping. Use a dedicated, network-isolated hypervisor instead.
Prerequisites
- A host with a type-2 hypervisor (VMware Workstation/Fusion or VirtualBox) or a dedicated type-1 host. At least 16 GB RAM and 200 GB disk for two guests.
- A victim guest (Windows 10/11) for detonation — e.g. built with FLARE-VM tooling.
- An analysis services guest (REMnux, Linux) to simulate internet services and capture traffic.
- Host networking able to provide a host-only / internal network with no NAT or bridged adapter on the victim.
Safety & Handling
- The victim VM must have no bridged or NAT adapter — host-only/internal only. All "internet" is simulated by the REMnux guest running INetSim.
- Disable shared folders, drag-and-drop, and clipboard sharing on the victim before detonation; these are escape and contamination paths.
- Take a clean base snapshot before any sample touches the VM and revert to it after every run.
- Store samples in password-protected archives (
infected) and only extract them inside the victim VM.
Workflow
Step 1: Create and harden the victim VM
Install Windows in a new VM, apply analysis tooling, then strip escape paths:
VM settings (victim):
Network adapter -> Host-only (vmnet1) or Internal network
Shared folders -> Disabled
Clipboard/DnD -> Disabled
USB controller -> Disabled
Snapshots -> enabled
Step 2: Stand up simulated internet on REMnux
On the REMnux guest (same host-only network), give it a static IP and run INetSim so the victim's DNS/HTTP/SMTP requests are answered locally:
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 · 141 lines · 60 tokens per session scan A 5ff7ce626718
setting-up-an-isolated-malware-analysis-lab is a skill published in the GitHub repository meltedinhex/analyst-ai-pack (22 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 60 tokens to every session and 1,247 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (asks for root). 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-linux-elf-malware
Analyze malicious Linux ELF binaries — botnets, cryptominers, ransomware, and rootkits targeting Linux servers, containers, and cloud infrastructure — through static analysis, dynamic tracing, and reverse engineering of x8664 and ARM samples. Use when investigating Linux malware, triaging a suspicious ELF binary…
dynamic-malware-analysis
Execute and analyze malware samples within a highly controlled, instrumented sandbox environment to observe their true behavior, network communications, file system modifications, and registry changes in real-time.
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.