Borrowing it
Nothing to install: this file belongs to gitpcl/openorchestrator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/gitpcl/openorchestrator/main/.claude/commands/wt-status.mdgit clone --depth 1 https://github.com/gitpcl/openorchestratorWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/gitpcl/openorchestrator/wt-status)<a href="https://agentmods.dev/commands/gitpcl/openorchestrator/wt-status"><img src="https://agentmods.dev/badge/commands/gitpcl/openorchestrator/wt-status/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/gitpcl/openorchestrator/wt-status"><img src="https://agentmods.dev/badge/commands/gitpcl/openorchestrator/wt-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00010 | $0.00383 |
| Opus 5.5 | $0.00004 | $0.00153 |
| Sonnet 5.5 | $0.00002 | $0.00077 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
wt-status 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 2mo 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
Worktree Claude Status
View Claude activity across all worktrees - see what each Claude session is working on, recent commands sent, and overall progress.
Current Context
Git worktrees:
!git worktree list 2>/dev/null || echo "No worktrees found"
tmux sessions (owt-*):
!tmux list-sessions 2>/dev/null | grep owt || echo "No owt sessions active"
Instructions
- Run:
owt status - Present the status table showing:
- Worktree name
- Branch
- Activity status (working/idle/blocked/waiting/completed)
- Current task description
- Number of commands sent to this worktree
- Last update time
- Highlight any worktrees that are blocked or have errors
- Show summary stats (how many active, idle, blocked)
- Suggest actions like:
- View detailed status:
owt status <worktree-name> - Set task:
owt status <worktree-name> --set-task "description" - Send command:
owt send <worktree-name> "your instruction" - Mark completed:
owt status <worktree-name> --set-status completed
- View detailed status:
Usage Examples
# View all worktree statuses
owt status
# View specific worktree in detail
owt status feature/auth
# Update what a worktree is working on
owt status feature/auth --set-task "Implementing OAuth flow"
# Mark a worktree as blocked
owt status feature/api --set-status blocked --notes "Waiting for API spec"
# Output as JSON for programmatic use
owt status --json
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.
- 2mo ago First seen · 54 lines · 10 tokens per session scan A 9b7830338c0c
wt-status is a command published in the GitHub repository gitpcl/openorchestrator (5 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 383 once invoked, about $0.0000 per session on Opus 5.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
diff-script
Compare an MDL script against the project's current state.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
Stage, commit, and optionally ship further. Pass an escalation token (push, pr, merge, squash, squash merge) to skip the prompt. With no token, commits then asks how far to ship. Delegates message format to the atomic-git-discipline skill.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
commit.zh-CN
A command for creating a Git commit, which is a saved checkpoint of changes in a Git project.
post-release.en
Read and execute the post-release skill from .agents/skills/post-release/SKILL.md.