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.
npx skills add emaraschio/cursor-commands --skill debug-issuegit clone --depth 1 https://github.com/emaraschio/cursor-commandsWrote 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.
[](https://agentmods.dev/skills/emaraschio/cursor-commands/debug-issue)<a href="https://agentmods.dev/skills/emaraschio/cursor-commands/debug-issue"><img src="https://agentmods.dev/badge/skills/emaraschio/cursor-commands/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.
<a href="https://agentmods.dev/skills/emaraschio/cursor-commands/debug-issue"><img src="https://agentmods.dev/badge/skills/emaraschio/cursor-commands/debug-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00010 | $0.00336 |
| Opus 5.5 | $0.00004 | $0.00134 |
| Sonnet 5.5 | $0.00002 | $0.00067 |
| Haiku 4.5 | $0.00001 | $0.00034 |
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 1mo 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.
What it actually says
Overview
Help debug the current issue in the code by walking through the debugging process systematically and providing clear, actionable solutions.
Steps
- Problem Analysis
- Identify the specific problem or error
- Understand the expected vs actual behavior
- Trace the execution flow to find the root cause
- Debugging Strategy
- Add appropriate logging statements
- Suggest debugging tools and techniques
- Identify key variables and states to monitor
- Recommend breakpoint locations
- Solution Approach
- Propose potential fixes with explanations
- Consider multiple solution approaches
- Evaluate trade-offs of different approaches
- Provide step-by-step resolution plan
- Prevention
- Suggest ways to prevent similar issues
- Recommend additional tests or checks
- Identify code patterns that could be improved
Debug Issue Checklist
- Identified the specific problem or error
- Understood expected vs actual behavior
- Traced execution flow to find root cause
- Added appropriate logging statements
- Proposed potential fixes with explanations
- Evaluated trade-offs of different approaches
- Provided step-by-step resolution plan
- Suggested ways to prevent similar issues
- Recommended additional tests or checks
Guardrails
- Reproduce and trace to the root cause before changing code.
- Change only the reported fault; do not touch unrelated code.
- Do not run destructive or production commands without explicit consent.
What ships with it
3 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.
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.
- 1mo ago First seen · 47 lines · 10 tokens per session scan A 10de6acbc47f
debug-issue is a skill published in the GitHub repository emaraschio/cursor-commands (9 stars, last pushed 2d ago), licensed MIT. It adds 10 tokens to every session and 336 once invoked, about $0.0000 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.
Other skills, from other repositories
cce-routing
Use Cursor Bridge's read-only cursorcontextengine for unfamiliar project understanding when the exact code location is unknown or the task requires tracing behavior, symbols, callers and callees, data flow, registrations, interface implementations, ownership boundaries, or cross-module relationships. Trigger for…
bisect
Use when hunting a regression, phrases like "bisect", "find the commit that broke X", "this used to work", "regression in test Y", "when did start". Also use when escalated from ci-debug-loop because log analysis can't pinpoint the offending change, or when a previously-passing test/build/behavior is now failing and…
review-performance
Use when the user explicitly asks for a performance review, benchmark review, profiling review, perf audit, pprof analysis, allocation review, latency regression check, hot-path review, throughput review, "is this fast enough", or "review perf". This skill is opt-in only — never run automatically as part of review-all…
ci-debug-loop
Watch a GitHub Actions CI run, diagnose failures from logs, apply fixes, re-push, and repeat until green or escalate. Use when CI is failing and the user wants to debug and fix it iteratively, or says "fix CI", "debug the build", or similar.
audit-performance
Audit and fix runtime performance (Core Web Vitals, load priority). Use when "slow page", "LCP/INP/CLS", "fetchpriority", "long tasks", or "bfcache". JS payload → audit-bundle-size. Instant nav → enhance-web-instant-nav. Load limits → test-load.
debug-sentry-monitor
Operate Sentry: triage and fix unresolved issues, cut noise, audit instrumentation, monitor after deploy. Use when "check Sentry", "review production errors", or "improve error tracking". One bug → workflow-fix-and-ship. Plan-only audit → plan-error-handling.