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/auto)<a href="https://agentmods.dev/commands/kaimingwan/oh-my-kiro/auto"><img src="https://agentmods.dev/badge/commands/kaimingwan/oh-my-kiro/auto/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/auto"><img src="https://agentmods.dev/badge/commands/kaimingwan/oh-my-kiro/auto.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.00606 |
| Opus 5.5 | $0.00000 | $0.00242 |
| Sonnet 5.5 | $0.00000 | $0.00121 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
auto 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.
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You MUST follow this exact sequence. @auto is a fully automated pipeline — no user confirmation between stages except during Expansion questions.
Stage 1: Expansion (Phase 0 + Readiness Check)
Follow skills/omk-planning/SKILL.md Phase 0 including Step 6: Readiness Check.
- Run the 4-dimension checklist (Goal / Constraints / Success Criteria / Context)
- If any dimension is ❌, ask the user ONE question (with Challenge Modes on 2nd+ question)
- Once all dimensions are ✅, generate a one-paragraph spec summarizing the validated understanding
touch .brainstorm-confirmed
Difference from @plan: @plan waits for explicit user confirmation after Phase 0. @auto proceeds automatically once Readiness Check passes.
Stage 2: Planning (Phase 1)
Read skills/omk-planning/SKILL.md Phase 1. Write plan to docs/plans/<date>-<slug>.md with Goal, Tasks (TDD structure), ## Review, and ## Checklist with verify commands.
Follow all Checklist Structure Rules from commands/plan.md Step 2.
Stage 3: Review (Phase 1.5 + Pre-mortem)
Follow skills/omk-planning/SKILL.md Phase 1.5:
- Run Pre-mortem Analysis — identify 3 failure risks (Integration / Assumption / Environment)
- Select review angles (2 fixed + 2 random = 4 reviewers)
- Dispatch 4 reviewer subagents in parallel with pre-mortem questions injected
Handling REQUEST CHANGES:
- @auto autonomously revises the plan based on reviewer feedback (max 2 revision rounds)
- After each revision, re-dispatch reviewers for the changed sections
- If still REQUEST CHANGES after 2 rounds: STOP and tell the user what remains unresolved. User must intervene manually.
Stage 4: Execution
After all reviewers APPROVE (or after user resolves remaining issues):
- Write plan path to
docs/plans/.active unlink .brainstorm-confirmed 2>/dev/null || true- Auto-commit plan artifacts (explicit file paths only, never
git add -A) - Run
@executeto launch task execution
Stage 5: Completion
When execution finishes:
- Report final status (completed / remaining / skipped items)
- If items remain, summarize what failed and suggest next steps
- Clean up
.activeif all items completed
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 · 50 lines · 0 tokens per session scan A 144ace81dfe2
auto 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 606 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.
auto compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| autoKaimingWan/oh-my-kiro | Command | 107 | 7mo ago | MIT | A | 0 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |