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/batteryshark/rekit/qiling-emulatenpx skills add batteryshark/rekit --skill qiling-emulategit clone --depth 1 https://github.com/batteryshark/rekitWrote 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/batteryshark/rekit/qiling-emulate)<a href="https://agentmods.dev/skills/batteryshark/rekit/qiling-emulate"><img src="https://agentmods.dev/badge/skills/batteryshark/rekit/qiling-emulate.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.00108 | $0.00771 |
| Opus 5 | $0.00054 | $0.00385 |
| Sonnet 5 | $0.00022 | $0.00154 |
| Haiku 4.5 | $0.00011 | $0.00077 |
Grade A, and why
qiling-emulate 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Binary Emulator (Qiling)
Contained tier — the binary runs on Qiling's emulated OS, not the host. Like
emulate-code, it is not behind the --allow-dynamic gate.
When to use — and why it's different from the others
The emulation/execution family now has three rungs:
| Skill | What runs the code | OS | Consent |
|---|---|---|---|
emulate-code |
Unicorn — raw bytes on a virtual CPU | none (memory only) | contained, no gate |
qiling-emulate |
Qiling — a full binary, OS syscalls emulated | emulated (BYO rootfs) | contained, no gate |
exec-observe / tracers |
the host runs it natively | real host OS | ⚡ consent-gated |
Reach for qiling-emulate when you have a whole binary (not just shellcode) that you
want to detonate without native execution and without a VM — including cross-arch /
cross-OS targets (run a Windows PE or an ARM ELF on your x86 macOS box). Qiling
implements the syscalls itself, so they hit the emulator, not your kernel.
What it does
Loads the target with Qiling against a rootfs, runs it under a wall-clock timeout
(emu_stop watchdog), and reports the outcome (completed / timeout / error),
detected arch, a best-effort syscall histogram, and the raw Qiling log tail (syscall/API
traces — the format varies by version, so the raw tail is always returned too).
Prerequisites
- Qiling (vendored):
rekit install qiling-emulate→scripts/build.shvendors it intoscripts/site. Heavier than Unicorn (pulls capstone/keystone/pefile/…). - A rootfs (BYO): grab one matching the target's OS/arch from
qilingframework/rootfs. Its libraries/DLLs
back the emulation. Without
--rootfsthe runner refuses with that hint (exit 3).
Safety note
Contained by default: file/network effects are emulated against the rootfs. Qiling can be configured for syscall/network passthrough — that widens the blast radius and is the operator's explicit choice, not what this skill does out of the box.
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.
- 4d ago First seen · 57 lines · 108 tokens per session scan A eac3aa0f403a
qiling-emulate is a skill published in the GitHub repository batteryshark/rekit (11 stars, last pushed 26d ago), licensed Apache-2.0. It adds 108 tokens to every session and 771 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…