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 mracal/vibe-engineering --skill debugging-journalgit clone --depth 1 https://github.com/mracal/vibe-engineeringWrote 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/mracal/vibe-engineering/debugging-journal)<a href="https://agentmods.dev/skills/mracal/vibe-engineering/debugging-journal"><img src="https://agentmods.dev/badge/skills/mracal/vibe-engineering/debugging-journal/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/mracal/vibe-engineering/debugging-journal"><img src="https://agentmods.dev/badge/skills/mracal/vibe-engineering/debugging-journal.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.00033 | $0.00418 |
| Opus 5.5 | $0.00013 | $0.00167 |
| Sonnet 5.5 | $0.00007 | $0.00084 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
vibe-debugging-journal 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 1mo 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.
This is a copy
100% identical to vibe-debugging-journal — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
vibe-debugging-journal
Bugs come in patterns. Recording them prevents re-investigation.
When to Use This Skill
- After resolving a non-trivial bug (took >10 minutes to find)
- After finding a bug that was hard to reproduce
- After debugging something where the root cause was surprising
- When you notice a bug pattern repeating
When NOT to Use This Skill
- Trivial bugs (typos, missing imports)
- Bugs with immediately obvious causes
- Build/configuration issues (not really bugs)
Steps
-
Categorize the bug:
- Concurrency (race conditions, deadlocks, ordering)
- State Management (stale state, missing updates, cache invalidation)
- Type/Validation (type errors, missing validation, edge cases)
- Integration (API mismatch, version incompatibility, protocol errors)
- Environment (platform-specific, config, deployment)
- UI/Rendering (layout, hooks, lifecycle)
-
Record in structured format:
### [Category]: [Short description]
**Date**: [date]
**Symptom**: [What was observed]
**Root Cause**: [The actual problem]
**Why Hard to Find**: [What made debugging difficult]
**Fix**: [What was changed]
**Prevention**: [How to prevent recurrence]
**Files**: [affected files]
-
Save to persistent storage:
- Project:
docs/debugging-journal.mdorDEBUGGING.md - Memory: Claude auto-memory or MCP
- Project:
-
Cross-reference — If this relates to an existing journal entry, link them
Output Format
Present the entry for user confirmation, then save. Keep entries concise (5-10 lines each).
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.
- 1mo ago First seen · 56 lines · 33 tokens per session scan A 01cc7039f08a
vibe-debugging-journal is a skill published in the GitHub repository mracal/vibe-engineering (3 stars, last pushed 7d ago), licensed MIT. It adds 33 tokens to every session and 418 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to vibe-debugging-journal, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
code-intelligence-contract
Use when dependency, call-chain, blast-radius, architecture, domain-flow, or unfamiliar-codebase analysis needs an optional vendor-neutral code-intelligence provider.
studio-context-brief
Use when an active KIT-managed Goal needs compact brief, working, or resume context projections from trusted structured state while preserving exact technical literals and durable handoff authority.
evidence-first-debugging
Use when debugging a crash, lỗi, failing game, tool, build, service, script, or reproducible local code failure requires repro or reproduction, giả thuyết or ranked hypotheses, instrumentation, root-cause isolation, a minimal fix, regression proof, and a regression test.
unity-ui-rendering-debugging
Use when a Unity UI, HUD, screen item, or NGUI widget is missing, clipped, behind another canvas, wrongly sorted, disconnected from a prefab or atlas, misanchored, or invisible despite correct gameplay state.
bug-hunt-swarm
Use when an unknown crash, intermittent failure, or cross-subsystem bug needs parallel read-only reproduction lanes, ranked hypotheses, suspect paths, and an integrator root-cause plan.
cpp-server-crash-triage
Use when triaging a C++ game server crash, dump, access violation, segmentation fault, stack trace, symbols, or build identity into a stable signature and ranked root-cause plan.