Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/slicervm/agent-skills/use-slicer)<a href="https://agentmods.dev/skills/slicervm/agent-skills/use-slicer"><img src="https://agentmods.dev/badge/skills/slicervm/agent-skills/use-slicer/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/slicervm/agent-skills/use-slicer"><img src="https://agentmods.dev/badge/skills/slicervm/agent-skills/use-slicer.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.00056 | $0.07807 |
| Opus 5 | $0.00028 | $0.03904 |
| Sonnet 5 | $0.00011 | $0.01561 |
| Haiku 4.5 | $0.00006 | $0.00781 |
Grade A, and why
use-slicer 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 — 690 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use Slicer — Launch Linux MicroVMs
Slicer gives you instant Linux microVMs through Firecracker on Linux and Apple Virtualization on macOS. Use it when you need:
- A real Linux environment with systemd, Internet access, and SSH preinstalled (especially from macOS)
- Sandboxed builds, CI, or E2E tests
- Docker/container workflows with port forwarding
- Isolated environments for untrusted or destructive operations
- Kubernetes (k3s) clusters for testing
- GPU/PCI passthrough workloads (via cloud-hypervisor backend)
- Automated code review pipelines in ephemeral microVMs
- Preparing one builder VM, then cold-forking clean runners without repeating setup
- Running coding agents in isolated microVMs (Amp, Claude Code, Codex, OpenCode, GitHub Copilot CLI) then copying out the outcome - code, files, reports, binaries, images, etc.
VMs boot in 1–3 seconds, have full systemd, internet access, and SSH pre-installed.
Docs: https://docs.slicervm.com
Go SDK: https://github.com/slicervm/sdk (github.com/slicervm/sdk)
On macOS, the CLI drives Slicer for Mac — a persistent Linux VM plus an sbox host group for sandboxes. See references/macos.md.
Install or update Slicer itself
Use Slicer's own installation and update paths. Never run arkade get slicer: Slicer is not an arkade tool. Use arkade for other CLI tools when
appropriate, including tools installed inside a guest, but do not infer that
it installs or upgrades Slicer.
Fresh Linux installation (and the Slicer CLI on macOS):
curl -sLS https://get.slicervm.com | sudo bash
Update an existing installation atomically, then verify it:
sudo slicer update
slicer version
For a non-destructive side-by-side version test, let the installed Slicer client fetch the correct OS/architecture binary into a temporary directory:
TEST_DIR=$(mktemp -d)
slicer update --version 0.1.216 --path "$TEST_DIR"
"$TEST_DIR/slicer" version
# Remove TEST_DIR after testing.
What ships with it
16 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.
- references/agent-sandboxes.md 6.2 KB
- references/arkade.md 3.4 KB
- references/bg-exec.md 3.4 KB
- references/cold-forking.md 7.1 KB
- references/custom-images.md 2.0 KB
- references/daemon-setup.md 9.7 KB
- references/file-transfer.md 4.0 KB
- references/headless-browser.md 8.1 KB
- references/headless-x11.md 8.5 KB
- references/interactive-tui.md 5.6 KB
- references/macos.md 4.1 KB
- references/networking.md 9.0 KB
- references/vm-names-and-tags.md 4.5 KB
- references/workflows.md 4.5 KB
- scripts/firefox-bidi.mjs 2.1 KB runs code
- scripts/firefox-bidi.py 5.1 KB runs code
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 · 690 lines · 56 tokens per session scan F 44d8c6e6a381
use-slicer is a skill published in the GitHub repository slicervm/agent-skills (5 stars, last pushed 4d ago), licensed MIT. It adds 56 tokens to every session and 7,807 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-31.
Other skills, from other repositories
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.
securing-kubernetes-on-cloud
This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
implementing-rbac-hardening-for-kubernetes
Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.
docker-socket-mount
Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.