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 oleg494/coding-kit --skill debug-incident-protocolgit clone --depth 1 https://github.com/oleg494/coding-kitWrote 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/oleg494/coding-kit/debug-incident-protocol)<a href="https://agentmods.dev/skills/oleg494/coding-kit/debug-incident-protocol"><img src="https://agentmods.dev/badge/skills/oleg494/coding-kit/debug-incident-protocol/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/skills/oleg494/coding-kit/debug-incident-protocol"><img src="https://agentmods.dev/badge/skills/oleg494/coding-kit/debug-incident-protocol.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.00126 | $0.01036 |
| Opus 5.5 | $0.00050 | $0.00414 |
| Sonnet 5.5 | $0.00025 | $0.00207 |
| Haiku 4.5 | $0.00013 | $0.00104 |
Grade A, and why
debug-incident-protocol 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Old cache looks like an unfixed bug** — first check that the server IS SERVING the fixed bytes (curl + grep of the fix marker line), then force the cache to die. How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug & incident protocol: facts before theories
1. Core: facts, not opinions
- FACTS BEFORE THEORIES — order: 1) config flags, 2) DB row, 3) log lines, 4) only then a code hypothesis. The first incident report contains a fact, not an opinion.
- SYMPTOM ≠ ROOT CAUSE — «minutes are not deducted» is a symptom; silent except + wrong parser is the root cause. Trace the call path to the side effect; fix the root cause ONCE.
- IF METRIC FLAT WHILE FEATURE «WORKS» — SILENT FAILURE — UX success + zero metric = swallowed error. Look for except/early return on the metric path.
- SINGLE CONSUMER FOR EXCLUSIVE STREAMS — long-poll/queue/lock file — one owner. Kill duplicates before start; health = exactly one PID.
- RESTART RITUAL IS PART OF THE FIX — code on disk ≠ code in memory. After the fix: stop all → start one → verify log. Check: PID creation time > edit time.
- ENCODING OF CONSOLE ≠ ENCODING OF PRODUCT — mojibake in the console does not mean corrupted data. Check UTF-8 in the client/file.
2. Localizing hangs
- «It can't hang» — not an argument. Anything can hang: a network without a timeout, an interactive prompt, an infinite loop.
- Localize with a progress marker — the marker («=== stage N ===») is printed at the START of the block → hang is INSIDE the last block with a marker.
- Progress — to a FILE, not a pipe —
cmd 2>&1 | Out-File prog.txt; a pipe can hang or lose the tail. - Isolate the suspect BEFORE the full run — one block with a small timeout (30-60s), not the whole set with 900s.
- Chain A && B && C masks the hang location — split stages: each command separately, its own timeout.
- First suspect — infrastructure, not logic — BeforeAll/modules/network/interactivity is guilty more often than an «instant» test.
- Compare with the last successful run — git diff: the culprit is usually in the changes.
3. Cache and «still broken»
- Old cache looks like an unfixed bug — first check that the server IS SERVING the fixed bytes (curl + grep of the fix marker line), then force the cache to die.
- Foreign processes on the port — a test instance on the port blocks the real launch → looks «broken».
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.
- 2d ago Changed bfbf03beea7a
- 8d ago Changed ea522e6b4bbd
- 11d ago Changed c2b734e88815
- 25d ago Changed 61010df275ae
- 26d ago Changed 93a982e79e9c
- 1mo ago Changed 7510aa3002b5
- 1mo ago Changed 6fcda5b775d2
- 1mo ago Changed 35ab83a6aa10
- 1mo ago Changed 13bbbbf208d3
- 1mo ago First seen · 54 lines · 126 tokens per session scan A 5fdb72b9834e
debug-incident-protocol is a skill published in the GitHub repository oleg494/coding-kit (3 stars, last pushed 2d ago), licensed MIT. It adds 126 tokens to every session and 1,036 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
spae-fix
Remediates pre-classified SPAE task gaps. Use after /check writes FIX.md and moves an active task to phase fix.
troubleshoot
Troubleshoot systematically: observe, hypothesize, test, fix, verify.
refactor
Refactor code to fix DRY, SOLID, and Structure violations while preserving behavior.
tracely
Instrument AI agents with Tracely and turn their production traces into CI gates. Use when the user mentions Tracely, tracely-ai, tracelysdk, the tracely CLI, or asks to trace/observe an AI agent, add LLM evaluators or LLM-as-a-judge columns, debug why a trace or conversation isn't showing up, wire agent regression…
debugging-livekit-agents
Drives a multi-turn conversation with a LiveKit agent running locally to see what it does. Use when the user says "test my agent", "try my agent", "does this work", "why did it call that tool", "it says the wrong thing when I ask X", "test this change", or whenever you have edited an agent and need to check how it…
gcloud-usage
This skill should be used when user asks about "GCloud logs", "Cloud Logging queries", "Google Cloud metrics", "GCP observability", "trace analysis", or "debugging production issues on GCP".