A bug-fixing skill that investigates errors, crashes, slowdowns, intermittent failures, and regressions, then explains their root cause and proposes a focused fix with a regression test.

Use it to analyse error messages, tracebacks, failing tests, race conditions, performance issues, and recently introduced bugs.

It turns a reported failure into a reproducible diagnosis and helps prevent the same problem from returning.

oma-debug — Skill for Claude Code and Codex by first-fluke

Install

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.

Any agent

npx skills add first-fluke/fullstack-starter --skill oma-debug

Clone the repo

git clone --depth 1 https://github.com/first-fluke/fullstack-starter

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/first-fluke/fullstack-starter/oma-debug/github.svg)](https://agentmods.dev/skills/first-fluke/fullstack-starter/oma-debug)

Your own site

<a href="https://agentmods.dev/skills/first-fluke/fullstack-starter/oma-debug"><img src="https://agentmods.dev/badge/skills/first-fluke/fullstack-starter/oma-debug/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/first-fluke/fullstack-starter/oma-debug"><img src="https://agentmods.dev/badge/skills/first-fluke/fullstack-starter/oma-debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,381 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

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.00030	$0.01381
Opus 5.5	$0.00012	$0.00552
Sonnet 5.5	$0.00006	$0.00276
Haiku 4.5	$0.00003	$0.00138

Measured 19d ago against content hash f6456470ab12, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

oma-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 19d 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.

Origin

This is a copy

100% identical to oma-debug — 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.

.agents/skills/oma-debug/SKILL.md · 145 lines

How it starts

The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Debug Agent - Bug Fixing Specialist

Scheduling

Goal

Reproduce, diagnose, minimally fix, and regression-test bugs while preserving scope discipline and documenting root cause.

Intent signature

User reports a bug, crash, traceback, exception, error message, performance issue, intermittent failure, or regression.
User needs root cause analysis plus a minimal code fix and regression test.

When to use

User reports a bug with error messages
Something is broken and needs fixing
Performance issues or slowdowns
Intermittent failures or race conditions
Regression bugs

When NOT to use

Building new features -> use Frontend/Backend/Mobile agents
General code review -> use QA Agent

Expected inputs

Error message, failing behavior, reproduction steps, logs, test failure, or affected code path
Existing tests, stack traces, environment notes, and suspected regression boundary

Expected outputs

Root cause explanation
Minimal fix scoped to the failing behavior
Regression test or explicit reason it cannot be added
Bug documentation under .agents/results/bugs/ when appropriate

Dependencies

resources/execution-protocol.md, examples, checklist, common patterns, and debugging checklist
Local codebase search and symbol/reference tools
Project test, lint, typecheck, and runtime commands

Control-flow features

Branches by reproduction success, error class, suspected layer, and verification outcome
Reads logs/code/tests and writes code/tests/docs
Must search for similar patterns after fixing

Structural Flow

Entry

Capture the reported symptom and suspected scope.
Reproduce or establish the closest reliable failing signal.
Identify affected files, tests, and related patterns.

Scenes

PREPARE: Gather symptoms, logs, reproduction path, and verification command.
ACQUIRE: Read failing code, tests, references, and similar patterns.
REASON: Isolate root cause and reject unsupported hypotheses.
ACT: Apply minimal fix and regression test.
VERIFY: Re-run failing and related checks.
FINALIZE: Document root cause, fix, test, and residual risk.

Read the full file on GitHub · 145 lines

Files

What ships with it

7 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.

Changes

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.

19d ago Changed · +1 lines f6456470ab12
1mo ago Changed · -5 lines · -12 tokens per session 439ee9fbea75
1mo ago First seen · 149 lines · 42 tokens per session scan A 079e3a4c5874

Subscribe to this mod's changes

oma-debug is a skill published in the GitHub repository first-fluke/fullstack-starter (224 stars, last pushed 6d ago), licensed MIT. It adds 30 tokens to every session and 1,381 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 oma-debug, differing in 0 lines, and is treated as a copy.

Debugging Testing Unit testing fastapi flutter gcp mise monorepo nextjs

pytest-suite

Write or extend the backend test suite following this project's conventions. Use when adding tests for a new service/route/repository, when coverage is missing, or when asked to test a feature. Knows the mocked-session + httpx AsyncClient setup so tests run with no database.

vstorm-co/full-stack-ai-agent-template · 59 tokens

oma-debug