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 agentmods add skills/emaraschio/cursor-commands/debug-issuenpx skills add emaraschio/cursor-commands --skill debug-issuegit clone --depth 1 https://github.com/emaraschio/cursor-commandsWhat 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.00010 | $0.00336 |
| Opus 5 | $0.00005 | $0.00168 |
| Sonnet 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 2d 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.
- 2d 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 26d ago), licensed MIT. It adds 10 tokens to every session and 336 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.
Other skills, from other repositories
cursor-delegate
Delegate bounded light-to-medium implementation, limited investigation, documentation, configuration, testing, and tooling work to Cursor Bridge after the primary agent owns the direction and risk boundaries. Use when a bounded Cursor pass can save primary-agent time, reduce omissions, or run alongside non-conflicting…
3d-web-experiences
Build distinctive, performant, production-grade 3D on the web with Three.js, React Three Fiber, and WebGL. Use when the user asks to "build a 3D scene", "add a 3D hero/landing", "make a product viewer/configurator", mentions three.js / react-three-fiber / r3f / drei / webgl / shaders, or asks to make an existing 3D…
minimax-m3-long-context
How to use MiniMax M3's 1M-token MSA context productively: what to load vs. compress, when to retrieve vs. ingest, how to keep skills shallow in the always-on prompt and deep in skills, and how to plan retention across iterations. Load when the task might exceed 200K tokens, when the user asks to "keep all of this in…
minimax-multimodal-toolkit
MiniMax-native multimodal workflow for image, video, voice, music, and media-processing tasks. Use when the user asks to generate image/video/audio assets, wants MiniMax-specific media APIs, needs TTS or voice workflows, wants reproducible local media outputs, or needs FFmpeg-style processing around generated media.…
review-all
Use when the user asks for a deep review, full review, comprehensive review, production readiness assessment, full audit, multi-domain audit, "security and reliability and code review", or "review everything". Also use when the user explicitly requests performance review alongside the comprehensive request (e.g.…
evaluate-dependency
Use when adding or evaluating a project dependency in any language, phrases like "should I use X library", "evaluate ", "what library for Y", or when reviewing a PR that touches a manifest (go.mod, package.json, requirements.txt, pyproject.toml, Cargo.toml, Gemfile, mix.exs, composer.json). Also use when comparing…