A debugging workflow that tests possible explanations for a bug using runtime evidence and structured reasoning.

It can use Sentry for production context and Firecrawl for researching fixes, then guide a multi-step investigation. API contract bugs and production monitoring have separate workflows.

It reduces guesswork by combining application evidence with step-by-step diagnosis and research into known fix patterns.

debug-issue — Command for Claude Code by kensaurus/cursor-kenji

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.

Clone the repo

git clone --depth 1 https://github.com/kensaurus/cursor-kenji

Made for: Claude Code.

Or install cursor-kenji, the plugin that ships this one along with the rest of its 132 skills, 63 commands, 6 agents, 1 hook, 3 MCP servers.

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/commands/kensaurus/cursor-kenji/debug-issue/github.svg)](https://agentmods.dev/commands/kensaurus/cursor-kenji/debug-issue)

Your own site

<a href="https://agentmods.dev/commands/kensaurus/cursor-kenji/debug-issue"><img src="https://agentmods.dev/badge/commands/kensaurus/cursor-kenji/debug-issue/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/commands/kensaurus/cursor-kenji/debug-issue"><img src="https://agentmods.dev/badge/commands/kensaurus/cursor-kenji/debug-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 227 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.00013	$0.00227
Opus 5.5	$0.00005	$0.00091
Sonnet 5.5	$0.00003	$0.00045
Haiku 4.5	$0.00001	$0.00023

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

Security

Grade A, and why

debug-issue 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 27d 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.

commands/debug-issue.md · 18 lines

What it actually says

/debug-issue

Hypothesis-driven debugging with runtime evidence — not guessing.

This command is a thin entry point. The full playbook lives in the debug-error skill: a hypothesis, a failing check, then a fix. When the error is from production and Sentry is connected, fetch that context first. When the fix pattern is unfamiliar, use Firecrawl or Context7.

Named /debug-issue (not /debug). Claude Code's bundled /debug and the Cursor CLI /debug both toggle debug logging or Debug mode. This command is the debugging procedure.

Use /debug-issue to explicitly enter debug mode. Otherwise, say "debug this", "investigate the bug", or "why isn't this working" and the skill auto-fires.

Related: debug-fe-be-integration for API/contract bugs, debug-sentry-monitor for production triage.

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.

27d ago Changed · +1 lines 77e06d94c383
28d ago Changed · -7 tokens per session bce1b58b5724
1mo ago First seen · 17 lines · 20 tokens per session scan A 73e02201393a

Subscribe to this mod's changes

debug-issue is a command published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 22d ago), licensed MIT. It adds 13 tokens to every session and 227 once invoked, about $0.0001 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-31.

Debugging agent-skills ai-agent claude cursor cursor-ai cursor-ide

debug-issue

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

/debug-issue

What this file has done since we first saw it

Other commands, from other repositories

lint-fix

fix-dependencies

analyze-deps

fix-issue

code-review

execute