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.
git clone --depth 1 https://github.com/cassler/awesome-claude-code-setupWrote 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/commands/cassler/awesome-claude-code-setup/debug-issue)<a href="https://agentmods.dev/commands/cassler/awesome-claude-code-setup/debug-issue"><img src="https://agentmods.dev/badge/commands/cassler/awesome-claude-code-setup/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/commands/cassler/awesome-claude-code-setup/debug-issue"><img src="https://agentmods.dev/badge/commands/cassler/awesome-claude-code-setup/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.00000 | $0.00835 |
| Opus 5.5 | $0.00000 | $0.00334 |
| Sonnet 5.5 | $0.00000 | $0.00167 |
| Haiku 4.5 | $0.00000 | $0.00084 |
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.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Issue
Please help me debug this issue: $ISSUE_DESCRIPTION
Error/symptom: $ERROR_MESSAGE Component/area (if known): ${COMPONENT:-unknown} When it started: ${TIMEFRAME:-recently} GitHub issue: ${ISSUE_NUMBER:-none} PR causing issue: ${PR_NUMBER:-unknown}
Systematic Debugging Workflow
-
Search for error patterns:
# Search for the exact error chs find-code "$ERROR_MESSAGE" # Search for related terms chs find-code "${RELATED_TERMS:-error exception fail}" -
Check recent changes:
# Get recent commit context ch ctx prepare-migration "debug $ISSUE_DESCRIPTION" # Show recent modifications chg log --oneline -20 -
Trace the problem area:
# Focus on suspected area ch ctx focus "${COMPONENT:-src}" 3 # Find related files chs find-file "*${COMPONENT}*" -
Analyze code flow:
- Trace imports:
ch cr imports-of "$SUSPECTED_FILE" - Find dependencies:
ch cr imported-by "$SUSPECTED_FILE" - Check for circular dependencies:
ch cr circular
- Trace imports:
-
Check test coverage:
# Find related tests chs find-file "*.test.*" | xargs grep -l "$COMPONENT" # Look for test failures ch ts test | grep -i "fail" -
Look for code quality issues:
# Check for TODOs and debug code ch cq todos --with-context | grep -C3 "$COMPONENT" ch cq console-logs -
Check related GitHub items:
# If issue number provided, get details if [ -n "$ISSUE_NUMBER" ]; then gh issue view "$ISSUE_NUMBER" fi # If PR number provided, check changes if [ -n "$PR_NUMBER" ]; then gh pr diff "$PR_NUMBER" | grep -C5 "$COMPONENT" fi # Search for related issues gh issue list --search "$ERROR_MESSAGE" --limit 5 -
Generate debugging report:
- Summarize findings
- Identify root cause
- Propose fix
- Note any side effects
- Link to issue/PR if applicable
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 · 117 lines · 0 tokens per session scan A 52b5e2c99a0b
debug-issue is a command published in the GitHub repository cassler/awesome-claude-code-setup (268 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 835 tokens. 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.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
react-native
Command "react-native" from getsentry/toolkit, covering examples, also associate with a release and distribution(s), xcode build step (react-native xcode) and important notes.
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.