What is debug-everything?

A whole-project debugging workflow for restoring a healthy build and test state. It addresses bugs, broken tests, continuous-integration failures, lint errors, type errors, formatting problems, and related infrastructure issues.

Use it to find and resolve all open bug tickets and validation failures, from formatting and linting through unit, end-to-end, and integration tests.

It gives projects with many simultaneous failures a complete repair process instead of handling only one symptom. It diagnoses problems first and fixes them in a defined dependency order.

debug-everything — Skill for Claude Code by navapbc

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add navapbc/digital-service-orchestra

Claude Code

/plugin install dso

Made for: Claude Code.

Or install dso, the plugin that ships this one along with the rest of its 37 skills, 4 commands, 53 agents.

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/navapbc/digital-service-orchestra/debug-everything/github.svg)](https://agentmods.dev/skills/navapbc/digital-service-orchestra/debug-everything)

Your own site

<a href="https://agentmods.dev/skills/navapbc/digital-service-orchestra/debug-everything"><img src="https://agentmods.dev/badge/skills/navapbc/digital-service-orchestra/debug-everything/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/navapbc/digital-service-orchestra/debug-everything"><img src="https://agentmods.dev/badge/skills/navapbc/digital-service-orchestra/debug-everything.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 22,647 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 original No closer match found 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.00131	$0.22647
Opus 5.5	$0.00052	$0.09059
Sonnet 5.5	$0.00026	$0.04529
Haiku 4.5	$0.00013	$0.02265

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

Security

Grade A, and why

debug-everything 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 2mo 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.

plugins/dso/skills/debug-everything/SKILL.md · 1,368 lines

How it starts

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

Debug Everything: Full Project Health Restoration

You are a Senior Software Engineer at Google brought in to restore a project to full health. The project has accumulated bugs, test failures, lint errors, type errors, CI failures, and possibly infrastructure issues. In addition to validation failures, you must resolve ALL open ticket issues of type bug. Your mandate is simple: find every problem and fix it, using disciplined engineering practices.

Mindset

You own everything. No "out of scope." Investigate and resolve all pre-existing failures using the fix-bug skill — "pre-existing" is a reason to fix, not skip.
Diagnose before treating. Run all diagnostics first. Understand the full landscape of failures before fixing anything.
TDD is selective, not reflexive. Behavioral bugs get a failing test BEFORE the fix. Mechanical fixes (imports, type annotations, config) rely on existing test coverage. See TDD Enforcement.
Never skip tests. Disabling, skipping, or deleting tests is never acceptable.
Fix in dependency order. Format > lint > type errors > unit tests > E2E > integration > infrastructure.
One logical fix at a time. One fix, verify, commit. No batching unrelated fixes.
Guard the orchestrator's context. The orchestrator is a coordinator, not a worker. Delegate ALL verbose operations (validation, diagnostics, auto-fixes, triage) to sub-agents. The orchestrator should only see compact summaries. Use model: "haiku" for validation-only sub-agents to minimize cost.

Usage

/dso:debug-everything                  # Full diagnostic + fix cycle
/dso:debug-everything --dry-run        # Diagnose only — create issues, no fixes
/dso:debug-everything --aws            # Include proactive AWS infrastructure scan in Phase B

Read the full file on GitHub · 1,368 lines

Files

What ships with it

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

2mo ago First seen · 1,368 lines · 131 tokens per session scan A 2f3fcc30b93f

Subscribe to this mod's changes

debug-everything is a skill published in the GitHub repository navapbc/digital-service-orchestra (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 131 tokens to every session and 22,647 once invoked, about $0.0005 per session on Opus 5.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-09-03.

Debugging E2E testing Testing Unit testing

debug-everything next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
debug-everythingnavapbc/digital-service-orchestra	Skill	6	yesterday	Apache-2.0	A	131	Claude Code
testing-blocksadobe/skills	Skill	324	today	Apache-2.0	A	61	Claude Code
diagnosing-bugsjellydn/my-ai-tools	Skill	128	yesterday	MIT	A	34	Claude Code
test-fixjerseycheese/agent-skills	Skill	4	2d ago	MIT	A	73	Claude Code
test-strategistData-Wise/craft	Skill	4	6d ago	MIT	A	63	Claude Code
regression-test-genEliyce/paqad-ai	Skill	8	today	MIT	A	44	Claude Code, Codex
test-masterzacklecon/claude-skills	Skill	3	29d ago	MIT	A	38	Claude Code, Codex