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.
npx agentmods add commands/kaimingwan/oh-my-kiro/debuggit 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/debug)<a href="https://agentmods.dev/commands/kaimingwan/oh-my-kiro/debug"><img src="https://agentmods.dev/badge/commands/kaimingwan/oh-my-kiro/debug.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 | $0.00000 | $0.01284 |
| Opus 5 | $0.00000 | $0.00642 |
| Sonnet 5 | $0.00000 | $0.00257 |
| Haiku 4.5 | $0.00000 | $0.00128 |
Grade A, and why
debug 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 5d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You MUST follow this exact sequence. @debug is a fully automated debugging pipeline — no user confirmation between stages. The goal is systematic root cause analysis, not guess-and-check.
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
Stage 0: Session Resume Check
Before starting any investigation, check for existing investigation documents:
- List
docs/investigations/— look for files matching the current bug topic - If a matching document exists:
- Read its Status Overview section to understand current state
- Read its Ruled Out section to avoid re-investigating dead ends
- Read its Decision Log to understand prior decisions
- Resume from the last recorded state — do NOT restart from scratch
- If no matching document exists:
- Create
docs/investigations/{date}-{topic}.mdusingskills/omk-debugging/investigation-template.mdas template - Fill in the Problem Statement with the user's bug report
- Create
Session Resume Protocol: Every new session MUST check docs/investigations/ first. The investigation document is the single source of truth for cross-session continuity.
Stage 1: Triage & Context
- Read
knowledge/episodes.md— check if this bug pattern has occurred before - Build Architectural Context around the bug:
generate_codebase_overview→ module structurefind_referenceson bug's core symbol(s) → all callersget_document_symbolson bug's file(s) → internal structure
- Classify failure type:
| Category | Signal |
|---|---|
| Logic/Semantic | Test fails, wrong output |
| Environment/Config | Works locally, fails elsewhere |
| Concurrency/Timing | Intermittent |
| Invalid Invocation | Schema error, 400 response |
| Under-specified Intent | Need more context |
- Write triage summary to the investigation document (
docs/investigations/{date}-{topic}.md):- Fill in Problem Statement
- Add initial entries to Evidence Table (L0 facts from diagnostics)
- Build initial Investigation Tree with top-level branches
- Update Status Overview with triage results and next steps
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.
- 5d ago First seen · 141 lines · 0 tokens per session scan A 81f78b8773a2
debug 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 1,284 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
git
Git operations with intelligent commit messages and workflow optimization.
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.