vm-config-commands

vm-config-commands is a command for Claude Code from macstadium/orka3-cli-agent-skill. It costs 0 tokens per session (972 once invoked), scanned A, original, Apache-2.0.

A reference for commands that create and configure virtual-machine templates in Orka3, a command-line system for managing virtual machines. It lists command syntax, required images, CPU and memory settings, scheduling, networking, and some Intel-only options.

In plain words
What is it for?
Use it to create VM configurations, choose an image, set CPU and RAM, attach an ISO, enable GPU passthrough, control VNC or networking, and check naming requirements.
Why use it?
It gives developers the exact command forms and configuration rules needed to create repeatable VM templates without searching through separate documentation.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

Good fit Use it to create VM configurations, choose an image, set CPU and RAM, attach an ISO, enable GPU passthrough, control VNC or networking, and check naming requirements.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/macstadium/orka3-cli-agent-skill/vm-config-commands
Install

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.

Clone the repo
git clone --depth 1 https://github.com/macstadium/orka3-cli-agent-skill

Made for: Claude Code.

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.

agentmods badge for vm-config-commands

README.md
[![agentmods](https://agentmods.dev/badge/commands/macstadium/orka3-cli-agent-skill/vm-config-commands/github.svg)](https://agentmods.dev/commands/macstadium/orka3-cli-agent-skill/vm-config-commands)
Your own site
<a href="https://agentmods.dev/commands/macstadium/orka3-cli-agent-skill/vm-config-commands"><img src="https://agentmods.dev/badge/commands/macstadium/orka3-cli-agent-skill/vm-config-commands/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.

agentmods 80×15 button for vm-config-commands

Your own site · 80×15
<a href="https://agentmods.dev/commands/macstadium/orka3-cli-agent-skill/vm-config-commands"><img src="https://agentmods.dev/badge/commands/macstadium/orka3-cli-agent-skill/vm-config-commands.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 972 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00972
Opus 5.5 $0.00000 $0.00389
Sonnet 5.5 $0.00000 $0.00194
Haiku 4.5 $0.00000 $0.00097

Measured yesterday against content hash 1099fc123bfc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

vm-config-commands 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 yesterday.

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.

orka3-cli/references/commands/vm-config-commands.md · 85 lines

How it starts

The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.

VM Configuration Commands Reference

This reference provides detailed syntax and examples for VM configuration template commands in the Orka CLI.

Scope: VM configs always live in orka-default and are visible to every user and service account with access to it. vm-config has no --namespace flag; pass -n on vm deploy instead.

No update command: there is no vm-config update. To change a config, delete and recreate it, or create it under a new name. Deleting a config that CI references breaks queued jobs, so roll changes blue/green: create the new name, repoint CI, then delete the old one. VMs don't record which config they were deployed from.

Sizing (Apple silicon): nodes run at most 2 VMs each, so size configs at about half a node's allocatable CPU and memory. Larger configs strand the second slot.

orka vm-config create (alias: vmc)

Create a VM configuration template.

Syntax:

orka vm-config create <NAME> [flags]

Options:

  • -i, --image string - (Required) Base image (local or OCI)
  • -c, --cpu int - Number of CPU cores (default: 3)
  • -m, --memory float - RAM in gigabytes. Max 32GB on 32GB nodes, 60GB on 64GB and 128GB nodes. If unset, defaults to a value based on the node with the least memory
  • --node string - Specific node for deployment
  • --scheduler string - Scheduler: 'default' or 'most-allocated'
  • --tag string - Node affinity tag
  • --tag-required - Require tagged nodes
  • --disable-vnc - Disable VNC. Locks you out unless the image has SSH or Screen Sharing enabled
  • --display-width int - Virtual display width, 320-3840 (3.4+)
  • --display-height int - Virtual display height, 480-2160 (3.4+)
  • --display-dpi int - Virtual display DPI, 60-320 (3.4+)

Intel-only options (Orka 3.6 and earlier, removed in Orka 4.0):

  • --iso string - ISO name to attach
  • --gpu - Enable GPU passthrough
  • --system-serial string - Custom serial number
  • --disable-net-boost - Disable network boost
  • --legacy-io - Legacy IO, required for High Sierra and Mojave VMs

Read the full file on GitHub · 85 lines

Changes

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.

  1. yesterday Changed · +14 lines 1099fc123bfc
  2. 2mo ago First seen · 71 lines · 0 tokens per session scan A 3f7ec56d486f

Subscribe to this mod's changes

vm-config-commands is a command published in the GitHub repository macstadium/orka3-cli-agent-skill (3 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 972 tokens. 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.