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/ckWrote 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/ck)<a href="https://agentmods.dev/commands/kaimingwan/oh-my-kiro/ck"><img src="https://agentmods.dev/badge/commands/kaimingwan/oh-my-kiro/ck/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/kaimingwan/oh-my-kiro/ck"><img src="https://agentmods.dev/badge/commands/kaimingwan/oh-my-kiro/ck.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.00000 | $0.00599 |
| Opus 5 | $0.00000 | $0.00300 |
| Sonnet 5 | $0.00000 | $0.00120 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
ck 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Checkout a branch in a submodule, with fuzzy search support. (CK = Checkout)
Scope
Operates on the current submodule or the submodule specified by the user.
Steps
Step 1: Determine Target Submodule
If user specifies a submodule name, use it. Otherwise detect from current directory:
# Check if we're inside a submodule
sm_path=$(git rev-parse --show-superproject-working-tree 2>/dev/null)
if [ -n "$sm_path" ]; then
echo "IN_SUBMODULE=true"
else
# List available submodules for user to pick
git submodule --quiet foreach 'echo $sm_path'
fi
Step 2: Fuzzy Search Branches
If user provided a branch name (or partial name after @ck):
input="<user_input>"
# Fetch latest branches
git fetch origin --prune --quiet 2>/dev/null
# Search: local branches first, then remote
echo "=== Local branches ==="
git branch --list "*${input}*" --sort=-committerdate | head -10
echo "=== Remote branches ==="
git branch -r --list "*${input}*" --sort=-committerdate | head -10
Show matches to user. If multiple matches, let user pick. If exactly one match, confirm and proceed.
If user provided NO branch name, show recent branches:
echo "=== Recent branches (last 10) ==="
git branch -r --sort=-committerdate | head -10
Step 3: Checkout
Two modes based on user intent:
Mode A: Direct checkout (switch submodule's current branch)
git checkout <branch>
Mode B: Create worktree (for development work)
branch="<selected_branch>"
sm_name=$(basename $(pwd))
wt_name="${sm_name}-$(echo $branch | sed 's#origin/##; s#/#-#g')"
wt_path="worktrees/${wt_name}"
# Create worktree at project root level
git worktree add "../../worktrees/${wt_name}" -b "$(echo $branch | sed 's#origin/##')" "$branch" 2>/dev/null \
|| git worktree add "../../worktrees/${wt_name}" "$branch"
echo "Worktree created: $wt_path (branch: $branch)"
Ask user which mode they want, default to Mode B (worktree) for feature branches.
Edge Cases
- Branch not found: Show "No branches matching ''. Did you mean:" with closest matches.
- Worktree already exists for branch: Warn and show existing worktree path.
- Detached HEAD in submodule: Warn user before checkout.
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.
- 9d ago First seen · 82 lines · 0 tokens per session scan A 9b8cd19213f6
ck 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 599 tokens. 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-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.