A structured way to find and fix the cause of a software failure. It repeatedly reproduces the problem, narrows it down, tests a possible explanation, applies a small fix, and checks the result.

Use it with an error, failing command, or reproducible bug when you can run the relevant local tests. It helps isolate the failing code path, test possible causes, make a minimal correction, and verify the behavior.

It reduces guesswork and avoids patches that only hide symptoms. It keeps a record of evidence and limits the number of investigation cycles.

debug — Skill for Claude Code and Codex by Oriolshhh: A structured way to find and fix the cause…

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.

agentmods

npx agentmods add skills/oriolshhh/runware-image-mcp/debug

Any agent

npx skills add Oriolshhh/runware-image-mcp --skill debug

Clone the repo

git clone --depth 1 https://github.com/Oriolshhh/runware-image-mcp

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/oriolshhh/runware-image-mcp/debug.svg)](https://agentmods.dev/skills/oriolshhh/runware-image-mcp/debug)

Your own site

<a href="https://agentmods.dev/skills/oriolshhh/runware-image-mcp/debug"><img src="https://agentmods.dev/badge/skills/oriolshhh/runware-image-mcp/debug.svg" alt="Measured on agentmods" height="20"></a>

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

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

Security scan A 0 findings. Scan, not verified.

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	$0.00019	$0.00708
Opus 5	$0.00010	$0.00354
Sonnet 5	$0.00004	$0.00142
Haiku 4.5	$0.00002	$0.00071

Measured 3d ago against content hash 48484f5ecacc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 3d 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 · 73 lines

How it starts

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

/debug — Diagnose and fix a failure

Purpose

Find and correct the causal defect rather than patching symptoms or cycling through speculative edits.

Invocation

/debug <symptom, failing command, error, or reproduction>

Accepted input

Observed and expected behavior, logs/errors, reproduction steps or command, environment, suspected area, and recent changes when known.

Prerequisites

A HarnessKit workspace and permission to run the relevant local reproduction and tests. Read the configured maximum with harnesskit loop list.

Procedure

Follow .agent/loops/debug-loop.yml, counting one full reproduce→investigate→hypothesize→experiment/fix→verify pass as one iteration:

Reuse a supplied context capsule; otherwise apply context-discovery once and construct a task-specific capsule before broad exploration.
Record expected/observed behavior, environment, and exact reproduction.
Reproduce without editing. Reduce the case and trace the narrowest failing path.
Maintain an evidence ledger and rank falsifiable hypotheses. Apply model-routing: a stable, localized reproduction may use standard/medium; retain heavy/high for ambiguous, cross-boundary, concurrent, security-sensitive, or repeatedly falsified investigations.
Run the highest-information controlled experiment, changing one variable.
If evidence identifies the root cause, add a regression test and apply the smallest safe fix. Otherwise begin the next iteration with the new evidence.
Verify the original reproduction, regression, adjacent behavior, and gates.
Stop immediately on verified success. At max_iterations, stop and return the ledger, remaining hypotheses, and next discriminating experiment.

Approval points

Ask before destructive, networked, credentialed, production, expensive, or externally visible diagnostics.
Requirement or public-contract changes return to /spec for approval.

Read the full file on GitHub · 73 lines

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.

3d ago First seen · 73 lines · 19 tokens per session scan A 48484f5ecacc

Subscribe to this mod's changes

debug is a skill published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 708 once invoked, about $0.0001 per session on Opus 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-31.

Debugging

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens