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 skills/oleg494/coding-kit/debug-incident-protocolnpx skills add oleg494/coding-kit --skill debug-incident-protocolgit clone --depth 1 https://github.com/oleg494/coding-kitWhat 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.00126 | $0.01020 |
| Opus 5 | $0.00063 | $0.00510 |
| Sonnet 5 | $0.00025 | $0.00204 |
| Haiku 4.5 | $0.00013 | $0.00102 |
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 yesterday.
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 — 51 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.
- yesterday First seen · 51 lines · 126 tokens per session scan A d532b474ab7f
debug-incident-protocol is a skill published in the GitHub repository oleg494/coding-kit (1 stars, last pushed 2d ago), licensed MIT. It adds 126 tokens to every session and 1,020 once invoked, about $0.0006 per session on Opus 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
run
Execute a named agent role with optimized instructions. Explicit invocation only ($run). Never trigger implicitly.
tip
Deliver a transformative life perspective shift and a productivity tip. Use when the user invokes /tip or wants non-technical inspiration or a fresh mental model.
agentic-security-review
Run a security and dependency audit for agent systems, tool-using AI apps, MCP/A2A integrations, or security-sensitive AI-generated code. Check slopsquatting risk, tool shadowing, rug pulls, memory/context poisoning, secrets, unsafe permissions, and common CWE patterns. Use when asked for security review, dependency…
agentic-spec
Create a structured specification before agentic coding work. Assemble the six context types, scale rigor for prototype/internal/production tasks, produce SPEC.md, and configure focused AGENTS.md boundaries. Use when asked to write a spec, plan a feature, design an agent/system, define architecture, or create…
agentic-evals
Design evaluation contracts and test plans for agentic systems. Create deterministic tests, trajectory evals, quality dimensions, gold-set criteria, and CI gates before or after implementation. Use when asked for tests first, an eval plan, success criteria, non-deterministic testing, LLM-as-judge setup, or…
agentic-production-readiness
Prepare an AI agent system for production operation. Cover SHIELD controls, sandbox/canary/production rollout, OpenTelemetry observability with GenAI semantic conventions, Agent Card drafting, governance, and post-deploy monitoring. Use for production readiness checks, go-live checklists, agent monitoring, agent…