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/wt-creategit 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.00014 | $0.00327 |
| Opus 5 | $0.00007 | $0.00163 |
| Sonnet 5 | $0.00003 | $0.00065 |
| Haiku 4.5 | $0.00001 | $0.00033 |
Grade A, and why
wt-create 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.
What it actually says
Create Worktree
Create a new git worktree with automatic tmux session and Claude Code startup.
Arguments
$ARGUMENTS - Branch name for the worktree (e.g., feature/add-login, bugfix/JIRA-123)
Current Context
Current branch:
!git branch --show-current 2>/dev/null || echo "Not on a branch"
Recent remote branches:
!git branch -r --list 2>/dev/null | head -10 || echo "No remote branches"
Existing worktrees:
!git worktree list 2>/dev/null || echo "No worktrees"
Instructions
- Run:
owt create $ARGUMENTS - Report the created worktree details:
- Path to the new worktree
- Branch name
- tmux session name
- Provide instructions for:
- Attaching to the tmux session:
owt tmux attach owt-<name> - Switching to the worktree:
cd $(owt switch <name>)
- Attaching to the tmux session:
Options
You can suggest additional flags based on user needs:
--base main- Create from a specific base branch--no-tmux- Skip tmux session creation--no-claude- Don't auto-start Claude Code--layout quad- Use a different tmux layout--attach- Automatically attach to the tmux session
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.
- 2d ago First seen · 44 lines · 14 tokens per session scan A 2226a6a0ddb4
wt-create is a command published in the GitHub repository gitpcl/openorchestrator (5 stars, last pushed 27d ago), licensed MIT. It adds 14 tokens to every session and 327 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）の計画・レビュー・実行・報告を自動化.