A diagnosis workflow for a failing test, broken build, crash, error, regression, or unexpected result. It reproduces the problem, narrows down the failing path, tests possible explanations, and reports the likely cause without editing code.

It is for investigating test failures, build failures, crashes, broken routes, and other reproducible software problems before handing the findings to a repair workflow.

It separates finding the cause from making a repair, so investigation does not hide the original problem or introduce temporary changes.

How aiblueprinthq/ai-blueprint configures Codex

Reuse

Borrowing it

Nothing to install: this file belongs to aiblueprinthq/ai-blueprint. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/aiblueprinthq/ai-blueprint/main/.agents/skills/debug/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/aiblueprinthq/ai-blueprint

Made for: 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/aiblueprinthq/ai-blueprint/debug/github.svg)](https://agentmods.dev/skills/aiblueprinthq/ai-blueprint/debug)

Your own site

<a href="https://agentmods.dev/skills/aiblueprinthq/ai-blueprint/debug"><img src="https://agentmods.dev/badge/skills/aiblueprinthq/ai-blueprint/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/aiblueprinthq/ai-blueprint/debug"><img src="https://agentmods.dev/badge/skills/aiblueprinthq/ai-blueprint/debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,478 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00059	$0.01478
Opus 5.5	$0.00024	$0.00591
Sonnet 5.5	$0.00012	$0.00296
Haiku 4.5	$0.00006	$0.00148

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

Security

Grade A, and why

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

.agents/skills/debug/SKILL.md · 159 lines

How it starts

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

debug - find the cause before changing the code

Context reuse: Reuse any required file already loaded in project instructions or the current session. Read it again only if absent, changed, or exact current bytes or line references are needed.

First action: Before project inspection, preflight, or any other tool call, publish running to blueprint/.state/run.json when blueprint/.state/ exists. From the project root, run the first helper that exists, node .agents/skills/blueprint-doctor/scripts/run-state.mjs or node .claude/skills/blueprint-doctor/scripts/run-state.mjs, with start --command <skill> --summary "<truthful summary>" --boundary <read-only|reviewed|local-only>. Use update at milestones, with --status blocked --resume <command> for a blocker, and finish --status ready|completed at the end; --help lists every option and blueprint/workflow.md has the full activity contract. A missing or failing helper is a warning, not a blocker.

Where this sits in the workflow:

reported failure  ->  [debug]  ->  /fix or /implement
(test, build,          (reproduce,    (spec a new fix, or
 crash, behavior)       isolate,       repair active work)
                        explain)

/debug separates diagnosis from repair. It gathers evidence, narrows the failure to a specific cause when possible, and stops with a useful handoff. It does not make the code "temporarily work" while investigating.

Input

Accept a symptom, failing command, error message, or unexpected behavior. Examples:

/debug npm test fails in cart-total.test.js
/debug the upload route returns 500 for PNG files
/debug why does the production build fail?

With no useful symptom, ask for the expected behavior, actual behavior, and smallest known reproduction. Do not guess which problem the user means.

Step 1 - establish the boundary

Read the project instructions and the context relevant to the failure:

AGENTS.md and its real commands
blueprint/context/project-overview.md
blueprint/context/coding-standards.md
blueprint/context/current-feature.md
the reported error, failing output, and affected files
git status, diff, and recent log when a regression is possible

Read the full file on GitHub · 159 lines

Files

What ships with it

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

agents/openai.yaml 227 B

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.

7d ago Changed · +7 lines 9b30c42dfb2b
2mo ago Changed · +2 lines · -45 tokens per session 569ac42017b3
2mo ago First seen · 150 lines · 104 tokens per session scan A a9b8cd708dba

Subscribe to this mod's changes

debug is a skill published in the GitHub repository aiblueprinthq/ai-blueprint (493 stars, last pushed 7d ago), licensed MIT. It adds 59 tokens to every session and 1,478 once invoked, about $0.0002 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-08-30.

Debugging

debug next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
debugaiblueprinthq/ai-blueprint	Skill	493	7d ago	MIT	A	59	Codex
systematic-debuggingopen-metadata/OpenMetadata	Skill	16k	yesterday	Apache-2.0	A	37	Claude Code
log-error-digestzebbern/claude-code-guide	Skill	4.7k	3d ago	MIT	A	71	Claude Code, Codex
cwv-optimizeradobe/skills	Skill	319	yesterday	Apache-2.0	A	112	Claude Code
ci-fixersipyourdrink-ltd/bernstein	Skill	1.2k	yesterday	Apache-2.0	A	15	Claude Code, Codex
incident-response-incident-responsermyndharis/antigravity-skills	Skill	1.9k	23d ago	MIT	A	36	Claude Code
triaging-web-analytics-supportPostHog/posthog	Skill	41k	yesterday	none	A	151	Claude Code, Codex

ai-blueprint: Skill for Codex