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.
npx agentmods add commands/gitpcl/openorchestrator/worktreegit clone --depth 1 https://github.com/gitpcl/openorchestratorWhat 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 | $0.00010 | $0.00382 |
| Opus 5 | $0.00005 | $0.00191 |
| Sonnet 5 | $0.00002 | $0.00076 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
worktree 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.
What it actually says
Worktree Management
Manage git worktrees for parallel development workflows.
Usage
/worktree create <branch>- Create new worktree with tmux session/worktree list- List all worktrees/worktree switch <name>- Switch to worktree/worktree delete <name>- Delete worktree/worktree cleanup- Clean stale worktrees/worktree sync- Sync worktrees with upstream
Current Context
Current git status:
!git status --short 2>/dev/null || echo "Not a git repository"
Current worktrees:
!git worktree list 2>/dev/null || echo "No worktrees found"
Active tmux sessions:
!tmux list-sessions 2>/dev/null | grep owt || echo "No owt sessions"
Instructions
Parse the user's subcommand from $ARGUMENTS and execute the appropriate owt command:
- create: Run
owt create <branch>- Creates worktree with tmux session and Claude Code - list: Run
owt list --all- Shows all worktrees with status - switch: Run
owt switch <name> --tmux- Switches to worktree's tmux session - delete: Run
owt delete <name>- Deletes worktree and its tmux session - cleanup: Run
owt cleanup- Shows stale worktrees (dry-run by default) - sync: Run
owt sync --all- Syncs all worktrees with upstream
After executing, provide a summary of the result and suggest next steps.
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.
- yesterday First seen · 42 lines · 10 tokens per session scan A 9044ab92daf3
worktree is a command published in the GitHub repository gitpcl/openorchestrator (5 stars, last pushed 27d ago), licensed MIT. It adds 10 tokens to every session and 382 once invoked, about $0.0001 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 commands, from other repositories
orchestrate
複数Issueを並列オーケストレーション（準備→開発→PR→マージ→UAT→修正ループ→完了）.
release
Command "release" from sageox/ox, covering release workflow, step 1: pre-flight checks, verify on main branch, clean working directory, run quality gates (run lint and tests in parallel) and step 1c: smoke tests (requires sageoxcipassword).
multi-stage-issue-review
Issue記載内容の多段階レビュー（通常→影響範囲）×2回と指摘対応を自動実行.
issue-enhance
Issue内容を分析し、ユーザーに質問しながら不足情報を補完・更新.
multi-stage-design-review
設計書の4段階レビュー（通常→整合性→影響分析→セキュリティ）と指摘対応を自動実行.
uat
実機受入テスト（UAT）の計画・レビュー・実行・報告を自動化.