admin-commands

A reference for Orka3 administrative commands that manage namespaces, user access, service accounts, and role-based permissions in an Orka cluster.

In plain words
What is it for?
Use it to create namespaces, move nodes, grant users access, manage service accounts, and configure role bindings and permissions.
Why use it?
It helps administrators set up isolated cluster areas and control who can use them without having to remember command syntax or naming rules.

Command

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.

agentmods
npx agentmods add commands/macstadium/orka3-cli-agent-skill/admin-commands
Clone the repo
git clone --depth 1 https://github.com/macstadium/orka3-cli-agent-skill
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 1,622 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.01622
Opus 5 $0.00000 $0.00811
Sonnet 5 $0.00000 $0.00324
Haiku 4.5 $0.00000 $0.00162

Measured 2d ago against content hash 644a5588dc20, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

admin-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 2d 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.

orka3-cli/references/commands/admin-commands.md · 205 lines

How it starts

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

Admin Commands Reference

This reference provides detailed syntax and examples for administrative Orka3 CLI commands including namespace management, RBAC, and service accounts.

Contents

Namespace Commands

orka3 namespace create

Create a new namespace.

Syntax:

orka3 namespace create <NAME> [--enable-custom-pods] [flags]

Options:

  • --enable-custom-pods - Configure for custom K8s resources (cannot run Orka VMs)

Name Requirements:

  • Begins with orka- prefix
  • Max 63 characters (including prefix)
  • Lowercase alphanumeric or dashes
  • Ends with alphanumeric
  • Unique to cluster

Post-Creation Steps:

  1. Move nodes: orka3 node namespace <NODE> <NAMESPACE>
  2. Grant access: orka3 rb add-subject --namespace <NS> --user <EMAIL>

Examples:

orka3 namespace create orka-test
orka3 namespace create orka-cp --enable-custom-pods

Note (fixed in 3.6.4): On --enable-custom-pods namespaces created before 3.6.4, users added via rb add-subject may be missing the orka-dev role binding. See references/troubleshooting/auth-issues.md.

orka3 namespace list

List all namespaces.

Syntax:

orka3 namespace list [<NAME>] [--output <FORMAT>] [flags]

Options:

  • -o, --output string - Output format: table|wide|json

orka3 namespace delete

Delete specified namespaces.

Syntax:

orka3 namespace delete <NAME> [<NAME2> ...] [--timeout <DURATION>] [flags]

Options:

  • -t, --timeout duration - Time to wait before giving up (default: 1h0m0s)

Prerequisites:

  • All VMs/pods must be removed
  • All nodes must be moved out

CAUTION: Destructive operation - cannot be undone.

Service Account Commands

orka3 serviceaccount create (alias: sa)

Create a service account in the specified namespace.

Syntax:

orka3 serviceaccount create <NAME> [--namespace <NS>] [flags]

Read the full file on GitHub · 205 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. 2d ago First seen · 205 lines · 0 tokens per session scan A 644a5588dc20

Subscribe to this mod's changes

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