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 skills add KaimingWan/oh-my-kiro --skill omk-debugginggit 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/skills/kaimingwan/oh-my-kiro/omk-debugging)<a href="https://agentmods.dev/skills/kaimingwan/oh-my-kiro/omk-debugging"><img src="https://agentmods.dev/badge/skills/kaimingwan/oh-my-kiro/omk-debugging.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.00081 | $0.04243 |
| Opus 5 | $0.00041 | $0.02122 |
| Sonnet 5 | $0.00016 | $0.00849 |
| Haiku 4.5 | $0.00008 | $0.00424 |
Grade A, and why
omk-debugging 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 — 422 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trigger Examples
- "这个测试跑不过"
- "why is this returning null?"
- "报错了，帮我看看"
- "build fails with exit code 1"
- "investigate why the hook isn't firing"
Systematic Debugging
Overview
Random fixes waste time and create new bugs. Quick patches mask underlying issues.
Core principle: ALWAYS find root cause before attempting fixes. Symptom fixes are failure.
Violating the letter of this process is violating the spirit of debugging.
The Iron Law
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
If you haven't completed Phase 1, you cannot propose fixes.
Three Iron Laws of Code Debugging
- No goto_definition = No modify — Don't change code you haven't navigated to its definition
- No find_references = No refactor — Don't refactor without knowing all usage sites
- No get_diagnostics = No claim fixed — Don't claim a fix without verifying zero new diagnostics
Investigation Document Protocol
The investigation document (docs/investigations/{date}-{topic}.md) is the persistent, cross-session record of a debugging effort. Create one at the start of every non-trivial debug session using skills/omk-debugging/investigation-template.md.
Three-Level Evidence System
| Level | Label | Meaning | Mutability |
|---|---|---|---|
| 🔒 L0 | Machine Facts | Command output, code analysis, API responses, experiment results | Immutable — cannot be overridden except by stronger L0 evidence |
| 👤 L1 | Human Observations | User-reported operations and phenomena | Protected — need L0 evidence + documented rationale to challenge |
| 🤖 L2 | Agent Inferences | AI deductions, hypotheses, analysis conclusions | Mutable — can be revised freely; mark old entry |
Section Update Rules
| Section | Update Mode | Rule |
|---|---|---|
| Status Overview | Overwrite | Refresh after every Stage completion — must reflect current state at all times |
| Evidence Table | Append-only | Never delete or edit existing entries; add new rows only |
| Investigation Tree | Overwrite | Update branch statuses (⬜→✅/❌) as investigation progresses |
| Decision Log | Append-only | Superseded decisions stay; mark status as "❌ 被 D{n} 取代" |
| Experiment Log | Append-only | Each experiment gets a unique EXP-{n} ID for cross-reference |
| Ruled Out | Append-only | Eliminated directions stay permanently to prevent re-investigation |
| Timeline | Append-only | Chronological milestones, never rewritten |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 422 lines · 81 tokens per session scan A c4399943f66c
omk-debugging is a skill published in the GitHub repository KaimingWan/oh-my-kiro (103 stars, last pushed 5mo ago), licensed MIT. It adds 81 tokens to every session and 4,243 once invoked, about $0.0004 per session on Opus 5. 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 skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.