Agent skill

Topology Mutation And Seat Management

by mvschwarz in mvschwarz/openrig

A skill your agent uses when changing a rig while it is alive — rig grow / rig expand / rig shrink / rig launch / rig remove / rig discover / rig bind / rig adopt / rig attach.

Apache-2.0Auto-check passedAgent Workflows

Install Topology Mutation And Seat Management

skills CLI
$ npx skills add mvschwarz/openrig --skill topology-mutation-and-seat-management -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mvschwarz/openrig topology-mutation-and-seat-management --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mvschwarz/openrig.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/_canonical/core/topology-mutation-and-seat-management .claude/skills/topology-mutation-and-seat-management && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
topology-mutation-and-seat-management
GitHub stars
6.8k
Token cost
~1.8k tokens
SKILL.md length
849 words
Files
1
Skills in repo
49
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when changing a rig while it is alive — rig grow / rig expand / rig shrink / rig launch / rig remove / rig discover / rig bind / rig adopt / rig attach.

  • Works in 4 steps: A newly created seat lacks the queue,… → Edges and permissions are not updated… → Adopt/bind succeeds at the tmux/session… → …
  • Agent Workflows work in your project
  • SKILL.md covers Use this when, Adding seats: rig grow first,…, Don't use this when and Failure modes (4), plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Topology Mutation And Seat Management is an agent skill from mvschwarz/openrig. Use when changing a rig while it is alive — rig grow / rig expand / rig shrink / rig launch / rig remove / rig discover / rig bind / rig adopt / rig attach. Covers the 4 failure modes (newly created seat lacks queue/startup/role; edges and permissions not updated; adopt/bind succeeds at tmux but not OpenRig identity; shrink/remove leaves stale topology references) and the rule that mutation must work while the rig is active, not just in clean fixtures.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows. It works with tmux. The repository describes itself as: Build your own network of agents from Claude Code, Codex and Pi: persistent teams with roles, shared context and owned work. The licence is Apache-2.0.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “/topology-mutation-and-seat-management”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. A newly created seat lacks the queue, startup context, or role files it needs to operate. Topology mutation creates the seat, but the seat…
  2. Edges and permissions are not updated when a seat is added or removed. Topology references go stale; later workflows route to nonexistent…
  3. Adopt/bind succeeds at the tmux/session layer but not at the OpenRig identity layer. The session is attached but rig whoami doesn't know…
  4. Shrink/remove leaves stale topology references that later workflows route into. Cleanup is part of the operation, not an afterthought.

What it can do on your machine

Read from SKILL.md and the folder at commit bed4d45. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Topology Mutation And Seat Management loads about 1.8k tokens when it runs. Until then it costs about 128 tokens; SKILL.md has 849 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~128
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mvschwarz/openrig at commit bed4d45, republished under its Apache-2.0 licence (© mvschwarz). 849 words, ~1,750 tokens.

Download SKILL.mdSave it as .claude/skills/topology-mutation-and-seat-management/SKILL.md (or your agent's skills folder).
name
topology-mutation-and-seat-management
description
Use when changing a rig while it is alive — `rig grow` / `rig expand` / `rig shrink` / `rig launch` / `rig remove` / `rig discover` / `rig bind` / `rig adopt` / `rig attach`. Covers the 4 failure modes (newly created seat lacks queue/startup/role; edges and permissions not updated; adopt/bind succeeds at tmux but not OpenRig identity; shrink/remove leaves stale topology references) and the rule that mutation must work while the rig is active, not just in clean fixtures.
metadata.cli_surfaces_referenced
adopt, attach, bind, discover, expand, grow, launch, ps, release, remove, shrink, unclaim, up, whoami

Topology Mutation and Seat Management

The ability to change a rig while it is alive: expand, shrink, launch, remove, discover, bind, adopt, and attach seats or sessions. Seat management includes the stable identifiers, edges, roles, and startup context that make those mutations coherent.

OpenRig should be easy to reach for. A user should be able to add capacity, retire capacity, adopt an existing session, or attach a terminal without rebuilding the whole topology. If mutation is rarely tested, users avoid it and the product collapses back into static launch scripts.

Use this when

  • Adding seats to a running rig (rig grow <rig-id> <member...> for the simple case, a fragment with rig expand or rig add otherwise; see below)
  • Removing capacity (rig shrink / rig remove)
  • Launching/relaunching a node in a running rig (rig launch)
  • Binding a discovered session into an existing logical node (rig bind)
  • Adopting a topology + binding live sessions (rig adopt)
  • Attaching a shell or agent into a rig node (rig attach --self)

Adding seats: rig grow first, a fragment when you need more

rig grow <rig-id> <member...> adds one or more seats to a running rig without writing YAML. Each seat gets the default agent spec and its default profile. Check rig grow --help on your installed version; at the time of writing:

  • --pod <pod>: the target pod; inferred when the rig has one pod
  • --new-pod <pod>: create a new pod for the seats (not together with --pod)
  • --runtime <runtime>: one runtime for every named seat (default claude-code)
  • --cwd <path>: one working directory for every named seat (default: the current directory)
  • --json: output for agents

Write a fragment instead when a seat needs something rig grow does not set: an explicit model, a permission policy, a different agent spec or role profile, a per-seat runtime or working directory, or startup files. Use rig expand <rig-id> <pod-fragment-path> to add a pod, or rig add <rig> <pod-namespace> <member-fragment-path> to add one member to an existing pod (<rig> is the rig id or its exact unique name).

Don't use this when

  • The rig is being created fresh from scratch — use rig up (lifecycle, not mutation)
  • The intent is to scale specifically (add specialized capacity) — use seat-scaling-and-specialization skill
  • The intent is occupant replacement on a stable seat — use seat-continuity-and-handover skill

Failure modes (4)

  1. A newly created seat lacks the queue, startup context, or role files it needs to operate. Topology mutation creates the seat, but the seat needs more than a tmux session to be useful.
  2. Edges and permissions are not updated when a seat is added or removed. Topology references go stale; later workflows route to nonexistent seats.
  3. Adopt/bind succeeds at the tmux/session layer but not at the OpenRig identity layer. The session is attached but rig whoami doesn't know about it; downstream consumers see partial state.
  4. Shrink/remove leaves stale topology references that later workflows route into. Cleanup is part of the operation, not an afterthought.
Show full SKILL.md (360 more words)Show less

Proof standard

Proof must cover mutation while a rig is active, not just in a clean test fixture. The useful matrix:

OperationWhat to verify
Add seatNew seat has queue, startup context, role; rig whoami resolves it
Remove seatStale references cleaned; edges/permissions updated
Adopt existing sessiontmux session bound at OpenRig identity layer; rig whoami reports correctly
Attach observer terminalExternal CLI attachment recorded
Verify topology projections after each moverig ps --nodes reflects current truth, not pre-mutation cache

A clean-fixture proof is necessary but not sufficient. Live-rig proof catches the failure modes that fixture-mode misses.

Stable roles during topology changes

Capacity changes must preserve useful roles, routing and durable work. Distinguish adding or removing a seat from replacing its occupant; use seat-continuity-and-handover for the latter.

Currently shipped surfaces

Per cli-reference.md v0.2.0:

  • rig grow <rig-id> <member...> [--pod <pod> | --new-pod <pod>] [--runtime <runtime>] [--cwd <path>] (added after v0.2.0; check rig grow --help)
  • rig expand <rig-id> <pod-fragment-path> (with optional session_source)
  • rig shrink <rigId> <podRef>
  • rig launch <rigId> <nodeRef>
  • rig remove <rigId> <nodeRef>
  • rig discover [--draft]
  • rig bind <discoveredId> --rig <rigId> (--node <id> | --pod <ns> --member <name>)
  • rig adopt <path> --bind <logicalId=tmuxSessionOrDiscoveryId>
  • rig attach --self --rig <rigId> --node <logicalId>
  • rig unclaim <sessionRef> / rig release <rigId>

Choose the proving environment and authority

Select an isolated active rig or an explicitly authorized live target for the relevant operation. Record its running build, before/after topology, continuity and outstanding work. A passing schema check or isolated fixture does not prove an existing live rig was changed correctly. A runtime timeout is indeterminate until its durable and process effects are reconciled; do not retry blindly.

The matrix above is verification guidance, not permission to modify another rig. Name the operation's owner and scope, preserve the state needed for recovery, and retain missing or failed checks in the result. No local experiment or unfinished proof obligation is implied by loading this skill.

See also

  • openrig-user skill — CLI surface for rig grow / expand / shrink / launch / remove / bind / adopt / attach
  • seat-scaling-and-specialization skill — when to add specialized capacity vs generic
  • seat-continuity-and-handover skill — replacing an occupant on a stable seat (different shape than topology mutation)
  • cross-host-rig-commands skill — cross-host topology mutation (deferred)

© mvschwarz, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/_canonical/core/topology-mutation-and-seat-management of mvschwarz/openrig.

Open the folder on GitHubat commit bed4d45

Compare with similar skills

Topology Mutation And Seat Management next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Topology Mutation And Seat Management compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Topology Mutation And Seat Management this skillmvschwarz/openrig6.8k—~1.8kAutomated safety check: PassApache-2.0
CodeGraph Agent Evalcolbymchenry/codegraph74k—~950Automated safety check: PassMIT
Agent of Empires Session Manageragent-of-empires/agent-of-empires3.3k—~2.5kAutomated safety check: PassMIT
Agent Deckasheshgoplani/agent-deck1.1k—~1.8kAutomated safety check: PassMIT
Agent of Empires Session Manageragent-of-empires/agent-of-empires3.3k—~2.1kAutomated safety check: PassMIT
Clawteamwin4r/ClawTeam-OpenClaw1.5k—~3.1kAutomated safety check: PassMIT

Similar skills

  • CodeGraph Agent Eval

    colbymchenry/codegraph

    Benchmarks how much CodeGraph helps a coding agent on a real repository, comparing runs with and without it for a chosen local or published version.

    74k GitHub stars~950 tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Agent of Empires Session Manager

    agent-of-empires/agent-of-empires

    Launches, monitors and organizes AI coding agent sessions such as Claude Code or Codex inside tmux, tracking status, capturing output and managing git worktrees for parallel branches.

    3.3k GitHub stars~2.5k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Agent Deck

    asheshgoplani/agent-deck

    agent-deck, the terminal session manager for AI coding agents.

    1.1k GitHub stars~1.8k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Agent of Empires Session Manager

    agent-of-empires/agent-of-empires

    Starts, monitors and organizes coding agent sessions that run in tmux through the aoe command, including groups, profiles and worktree-based parallel work.

    3.3k GitHub stars~2.1k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Clawteam

    win4r/ClawTeam-OpenClaw

    Multi-agent swarm orchestration. An agent skill from win4r/ClawTeam-OpenClaw.

    1.5k GitHub stars~3.1k tokensUpdated 3 mo ago
    Agent WorkflowsAuto-check passed
  • Fleet Manager for Agent Sessions

    asgeirtj/system_prompts_leaks

    Shows one digest of coding-agent sessions across your connected machines and lets you open, read, steer, approve, stop and close them, over Herdr, tmux or MSP.

    69k GitHub stars~2.5k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from mvschwarz/openrig

All 49 skills in this repo
  • OpenRig Upgrade Procedure

    mvschwarz/openrig

    Walks an agent through upgrading the OpenRig CLI and daemon one observed step at a time, keeping live seats alive and reconciling managed plugin files.

    6.8k GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Agent Refocusing

    mvschwarz/openrig

    Re-grounds a long-running agent in the current product outcome by running a path-based trace to the root of its topology and work trees.

    6.8k GitHub stars~864 tokensUpdated today
    Auto-check passed
  • OpenRig Software Factory

    mvschwarz/openrig

    Helps set up a continuing agent software team for a real repository with OpenRig, choosing between manual work, queue handoffs and an explicit Workflow.

    6.8k GitHub stars~2.6k tokensUpdated today
    Auto-check passed
  • Separates a stable agent seat's identity from its changing occupant, and records honest, two-part provenance whenever one occupant replaces another.

    6.8k GitHub stars~2.5k tokensUpdated today
    Auto-check passed
  • Loads one section of a Markdown file by its path#h2-slug address with a bundled resolver script, for use outside OpenRig's context library.

    6.8k GitHub stars~341 tokensUpdated today
    Auto-check passed
  • Agent Starters

    mvschwarz/openrig

    Covers authoring, inspecting, refreshing, promoting and deprecating named Agent Starters, the reusable starting points for agent seats in a rig.

    6.8k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Topology Mutation And Seat Management

What does Topology Mutation And Seat Management do?

A skill your agent uses when changing a rig while it is alive — rig grow / rig expand / rig shrink / rig launch / rig remove / rig discover / rig bind / rig adopt / rig attach. Topology Mutation And Seat Management is an agent skill from mvschwarz/openrig. Use when changing a rig while it is alive — rig grow / rig expand / rig shrink / rig launch / rig remove / rig discover / rig bind / rig adopt / rig attach.

When should I use Topology Mutation And Seat Management?

Topology Mutation And Seat Management fits situations like: agent Workflows work in your project.

How do I install Topology Mutation And Seat Management in Claude Code?

Run `npx skills add mvschwarz/openrig --skill topology-mutation-and-seat-management -a claude-code`. Or copy the skill folder (skills/_canonical/core/topology-mutation-and-seat-management in mvschwarz/openrig) into .claude/skills/topology-mutation-and-seat-management in your project. Claude Code loads it when a task matches its description.

How do I install Topology Mutation And Seat Management in Codex?

Run `npx skills add mvschwarz/openrig --skill topology-mutation-and-seat-management -a codex`. Or copy the skill folder (skills/_canonical/core/topology-mutation-and-seat-management in mvschwarz/openrig) into .agents/skills/topology-mutation-and-seat-management in your project. Codex loads it when a task matches its description.

Can I use Topology Mutation And Seat Management in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mvschwarz/openrig --skill topology-mutation-and-seat-management -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/topology-mutation-and-seat-management, .gemini/skills/topology-mutation-and-seat-management, .github/skills/topology-mutation-and-seat-management and .opencode/skills/topology-mutation-and-seat-management in your project.

What does Topology Mutation And Seat Management need to run?

SKILL.md names no scripts, command-line tools or credentials: Topology Mutation And Seat Management is instructions for the agent only.

Does Topology Mutation And Seat Management access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Topology Mutation And Seat Management safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Topology Mutation And Seat Management use?

Topology Mutation And Seat Management is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Topology Mutation And Seat Management use?

About 1.8k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Topology Mutation And Seat Management?

Skills that share tags, products or a category with Topology Mutation And Seat Management: CodeGraph Agent Eval (colbymchenry/codegraph, 74k stars), Agent of Empires Session Manager (agent-of-empires/agent-of-empires, 3.3k stars), Agent Deck (asheshgoplani/agent-deck, 1.1k stars) and Agent of Empires Session Manager (agent-of-empires/agent-of-empires, 3.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Topology Mutation And Seat Management?

mvschwarz (a GitHub user) maintains it in mvschwarz/openrig, which has 6,785 GitHub stars. The repository holds 49 skills in this directory. The repository was last updated on October 11, 2026.

Source: mvschwarz/openrig on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.