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-worktrees)<a href="https://agentmods.dev/skills/slicervm/agent-skills/use-slicer-worktrees"><img src="https://agentmods.dev/badge/skills/slicervm/agent-skills/use-slicer-worktrees/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-worktrees"><img src="https://agentmods.dev/badge/skills/slicervm/agent-skills/use-slicer-worktrees.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.00058 | $0.01879 |
| Opus 5 | $0.00029 | $0.00940 |
| Sonnet 5 | $0.00012 | $0.00376 |
| Haiku 4.5 | $0.00006 | $0.00188 |
Grade A, and why
use-slicer-worktrees 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 5d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slicer Worktrees — git worktrees and repos inside a microVM
For coding agent sandboxes, prefer slicer <agent> --worktree [path]: it launches the VM, pushes a git worktree with a working, self-contained .git, installs the agent into that path, and attaches in one command.
Use lower-level slicer wt push when you are working with a plain VM, reusing a separately created VM, or need explicit control over the push/pull lifecycle. The host repository is never mounted and its hooks never run inside the VM.
This skill assumes a running Slicer daemon — see the use-slicer skill for connecting to one.
Why slicer wt (and not a plain copy)
A git worktree's .git is a file, not a directory:
gitdir: /home/you/src/project/.git/worktrees/feature-x
That is an absolute host path. Tar-copying the worktree directory into a VM leaves the pointer dangling — every git command in the VM fails with fatal: not a git repository. And even for a normal repo, copying .git wholesale drags host hooks and config along.
Worktree mode and slicer wt push stage a fresh, sanitised .git instead, so git works correctly in the VM and the host repo stays untouchable.
Quick start
slicer codex --worktree . # launch a persistent Codex VM and push the current worktree in
# ...let the agent work and commit in the VM...
slicer wt pull <vm> . # commits + files back, your branch fast-forwarded
git push # from the host, under your own identity
<vm> is the VM name printed by the agent command. Use slicer amp, slicer claude, slicer copilot, slicer opencode, slicer pi, or slicer workspace the same way. Use --rm when you want a disposable VM; worktree and agent sandboxes are persistent by default.
Commands
| Command | Purpose |
|---|---|
slicer codex --worktree [path] |
Launch/provision Codex, push path as a git worktree, and attach |
slicer codex --wt [path] |
Alias for --worktree |
slicer workspace --worktree [path] |
Launch a clean shell VM with a pushed worktree and no coding agent |
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.
- 5d ago Changed · +1 lines 906723780fba
- 10d ago First seen · 136 lines · 58 tokens per session scan A 069244954f90
use-slicer-worktrees is a skill published in the GitHub repository slicervm/agent-skills (5 stars, last pushed 4d ago), licensed MIT. It adds 58 tokens to every session and 1,879 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.