Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/KaimingWan/oh-my-kironpx agentmods add commands/kaimingwan/oh-my-kiro/wtWrote 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/kaimingwan/oh-my-kiro/wt)<a href="https://agentmods.dev/commands/kaimingwan/oh-my-kiro/wt"><img src="https://agentmods.dev/badge/commands/kaimingwan/oh-my-kiro/wt.svg" alt="Measured on agentmods" 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.00000 | $0.00616 |
| Opus 5 | $0.00000 | $0.00308 |
| Sonnet 5 | $0.00000 | $0.00123 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade C, and why
wt scanned grade C with 1 finding 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 8d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Use `git -C <submodule> worktree remove` (not rm -rf) How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage worktrees: list status, clean up merged branches.
Step 1: List all worktrees with status
Run:
echo "=== Worktrees in worktrees/ ==="
for dir in worktrees/*/; do
[ -d "$dir" ] || continue
dir="${dir%/}"
BRANCH=$(git -C "$dir" rev-parse --abbrev-ref HEAD 2>/dev/null || echo "unknown")
echo " $dir → branch: $BRANCH"
done
Step 2: Check merge status
For each worktree, detect its submodule by reading .git file and check merge status:
for dir in worktrees/*/; do
[ -d "$dir" ] || continue
dir="${dir%/}"
NAME=$(basename "$dir")
BRANCH=$(git -C "$dir" rev-parse --abbrev-ref HEAD 2>/dev/null || continue)
# Detect submodule from worktree's git common dir
COMMON=$(git -C "$dir" rev-parse --git-common-dir 2>/dev/null)
SM=$(basename "$(dirname "$COMMON")" 2>/dev/null)
[ -d "$SM" ] || { echo " ⚠️ $dir — cannot detect submodule, skipping"; continue; }
# Check if branch is merged into main
git -C "$SM" fetch origin main --quiet 2>/dev/null
if git -C "$SM" branch --merged origin/main 2>/dev/null | grep -q "$BRANCH"; then
echo " ✅ $dir ($BRANCH) — MERGED into $SM/main → safe to remove"
else
echo " 🔄 $dir ($BRANCH) — NOT merged into $SM/main"
fi
done
Step 3: Confirm and clean up
Show the list to the user. For worktrees marked "MERGED":
- Ask user to confirm which ones to remove
- For each confirmed removal:
git -C <submodule> worktree remove ../worktrees/<name>
- If
.active-submoduleexists and its worktree field matches the removed path, clear it:
if [ -f .active-submodule ] && command -v jq >/dev/null 2>&1; then
WT=$(jq -r '.worktree // ""' .active-submodule 2>/dev/null)
[ "$WT" = "worktrees/<name>" ] && : > .active-submodule
fi
Important rules
- Only manage worktrees under
worktrees/directory (not external paths) - Always confirm with user before removing — never auto-delete
- Use
git -C <submodule> worktree remove(not rm -rf)
User's message (the text after @wt):
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.
- 8d ago First seen · 65 lines · 0 tokens per session scan C c13594d14966
wt is a command published in the GitHub repository KaimingWan/oh-my-kiro (103 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 616 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
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.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
handoff
Export a Waybill Bundle by default, or import one when requested.