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-cleanupgit 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.00011 | $0.00250 |
| Opus 5 | $0.00005 | $0.00125 |
| Sonnet 5 | $0.00002 | $0.00050 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
wt-cleanup 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
Cleanup Stale Worktrees
Identify and remove worktrees that haven't been accessed recently.
Current Context
All worktrees:
!git worktree list 2>/dev/null || echo "No worktrees"
Instructions
-
First, run a dry-run to show what would be cleaned:
owt cleanup --days 14 -
Show the user the list of stale worktrees found, including:
- Path
- Branch name
- Last accessed date
- Status (uncommitted changes, unpushed commits)
-
If stale worktrees are found and user confirms cleanup:
owt cleanup --no-dry-run -y -
Report cleanup results:
- Number cleaned
- Number skipped (protected due to uncommitted changes)
- Any errors
Options
--days 7- Change the staleness threshold--force- Include worktrees with uncommitted changes--no-dry-run- Actually delete (default is dry-run)
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 · 43 lines · 11 tokens per session scan A 0406d05f56f1
wt-cleanup is a command published in the GitHub repository gitpcl/openorchestrator (5 stars, last pushed 28d ago), licensed MIT. It adds 11 tokens to every session and 250 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→修正ループ→完了）.
issue-enhance
Issue内容を分析し、ユーザーに質問しながら不足情報を補完・更新.
multi-stage-issue-review
Issue記載内容の多段階レビュー（通常→影響範囲）×2回と指摘対応を自動実行.
feature-design
Use this skill when a user wants to think through, design, or spec out a feature, product decision, or technical capability. Triggers include: "I'm thinking about adding X", "help me design Y", "let's spec out Z", "what should I consider for this feature", or any request to reason through a change before building it.…
uat
実機受入テスト（UAT）の計画・レビュー・実行・報告を自動化.
issues-exec-plan
複数Issueの並列作業可否を分析し、実行計画をまとめるエピックIssueを作成.