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.
git clone --depth 1 https://github.com/KaimingWan/oh-my-kiroWrote 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/evaluate)<a href="https://agentmods.dev/commands/kaimingwan/oh-my-kiro/evaluate"><img src="https://agentmods.dev/badge/commands/kaimingwan/oh-my-kiro/evaluate/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/evaluate"><img src="https://agentmods.dev/badge/commands/kaimingwan/oh-my-kiro/evaluate.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.01514 |
| Opus 5.5 | $0.00000 | $0.00606 |
| Sonnet 5.5 | $0.00000 | $0.00303 |
| Haiku 4.5 | $0.00000 | $0.00151 |
Grade A, and why
evaluate scanned grade A 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 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
grep -rn 'subprocess\|eval\|exec\|open(\|os.system' <modified files> How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Step 1: Resolve evaluation target
- If the user specifies a path after @evaluate (e.g.,
@evaluate worktrees/omk-foo), use that path. - Otherwise, check
.active-submodule:
if [ -f .active-submodule ]; then
jq -r '.worktree // empty' .active-submodule
fi
- If a worktree path is found, use it. Otherwise, use project root.
Set the resolved path as EVAL_DIR.
Step 2: Gather context
cd "$EVAL_DIR"
PLAN=$(cat docs/plans/*.md 2>/dev/null | head -200)
DIFF=$(git diff --stat && git diff)
[ -z "$DIFF" ] && DIFF=$(git diff --cached --stat && git diff --cached)
Step 3: Dispatch 4 parallel evaluator subagents
Dispatch ALL 4 subagents in parallel (one use_subagent call with 4 entries). Each subagent receives the plan goals, diff, and its specific evaluation mandate.
Every subagent MUST:
- Fill ALL mandatory tables — empty or missing table rows = REJECTED, re-dispatch
- Answer its Canary question (proves source code was actually read)
- Classify each finding: CRITICAL / HIGH / MEDIUM / LOW
- End with exactly:
Verdict: PASSorVerdict: FAIL - Missing verdict = malformed → REJECTED, re-dispatch
Subagent #1: "Refactoring Expert" — Simplicity + Maintainability
Persona: A senior engineer who believes the best code is code that doesn't exist. Your job is to find things to delete or simplify.
Read all modified files in EVAL_DIR. Then fill EVERY table below — empty table = REJECTED.
Table A — Long functions (>50 lines):
| Function | File:Line | Lines | Can split? | Split plan | Reason if not |
|---|
If no functions >50 lines, write one row: "None found — all functions ≤50 lines."
Table B — Exception handling:
| Location (file:line) | Catches what | Necessary? | What if removed |
|---|
If no try/except blocks, write one row: "No exception handlers found."
Table C — Abstraction layers:
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 · 169 lines · 0 tokens per session scan A 66a22586d9de
evaluate is a command published in the GitHub repository KaimingWan/oh-my-kiro (107 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,514 tokens. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
evaluate compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| evaluateKaimingWan/oh-my-kiro | Command | 107 | 7mo ago | MIT | A | 0 | Claude Code |
| diff-reviewcoco-research/coco | Command | 785 | yesterday | Apache-2.0 | A | 11 | Claude Code |
| review-branchdamusix/atomic-claude | Command | 115 | 5d ago | MIT | A | 35 | Claude Code |
| refactorRchGrav/claudebox | Command | 1.2k | 1mo ago | MIT | A | 9 | Claude Code |
| spec-trace-requirementsrjmurillo/ai-agents | Command | 49 | yesterday | MIT | A | 0 | GitHub Copilot |
| merge-conflict-analysisrjmurillo/ai-agents | Command | 49 | yesterday | MIT | A | 0 | GitHub Copilot |
| initazrtydxb/procoder | Command | 211 | 11d ago | Apache-2.0 | A | 16 | Claude Code |