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.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.00606 |
| Opus 5 | $0.00000 | $0.00303 |
| Sonnet 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 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.
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.
- 8d 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 (103 stars, last pushed 5mo 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.