shell

A command that opens an interactive shell inside a selected orchestra member's worktree, an isolated working copy of a code branch.

In plain words
What is it for?
Use it to work on a named branch, choose a worktree with fzf, attach to a tmux session, or run one command such as tests and exit.
Why use it?
It gives you a terminal with that branch's files and environment settings already selected, so commands run in the intended workspace.

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/mirinodev/maestro/shell
Clone the repo
git clone --depth 1 https://github.com/mirinodev/maestro
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,024 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.01024
Opus 5 $0.00000 $0.00512
Sonnet 5 $0.00000 $0.00205
Haiku 4.5 $0.00000 $0.00102

Measured yesterday against content hash 83279a6821ce, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

shell 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.

docs/commands/shell.md · 169 lines

How it starts

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

🔸 shell

Enter an interactive shell session in an orchestra member.

Overview

The shell command provides an interactive shell environment within a specific worktree. This allows you to work directly in the context of a feature branch with all environment variables properly set.

Usage

mst shell [branch-name] [options]
mst sh [branch-name] [options]  # alias

Options

  • --fzf - Interactively select orchestra member with fzf
  • --cmd <command> - Execute command and exit (non-interactive)
  • --tmux - Attach to existing tmux session (create if doesn't exist)
  • --tmux-vertical, --tmux-v - Open shell in vertical split pane
  • --tmux-horizontal, --tmux-h - Open shell in horizontal split pane

Examples

Basic Usage

Enter a shell in a specific orchestra member:

# Enter shell
mst shell feature/awesome

# Using alias
mst sh feature/api

Interactive Selection

Use fzf to select which orchestra member to enter:

# Select with fzf
mst shell --fzf

# Shorthand without branch name
mst sh --fzf

Execute Command and Exit

Run a single command without entering interactive shell:

# Run tests and exit
mst shell feature/test --cmd "npm test"

# Check Node version
mst shell backend --cmd "node --version"

tmux Integration

Work with tmux for better session management:

# Attach to existing tmux session or create new
mst shell feature/ui --tmux

# Open in vertical split (side by side)
mst shell feature/api --tmux-v

# Open in horizontal split (top and bottom)
mst shell feature/db --tmux-h

# Combine with fzf
mst shell --fzf --tmux-v

Environment Variables

When in a maestro shell, these environment variables are automatically set:

  • MAESTRO - Set to "1" (indicates you're in a maestro shell)
  • MAESTRO_BRANCH - The branch name of current worktree
  • MAESTRO_PATH - The absolute path to the worktree

Shell Customization

The shell prompt is automatically customized to show the current orchestra member:

Read the full file on GitHub · 169 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 First seen · 169 lines · 0 tokens per session scan A 83279a6821ce

Subscribe to this mod's changes

shell is a command published in the GitHub repository mirinodev/maestro (9 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,024 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.