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 commands/cassler/awesome-claude-code-setup/debug-issuegit clone --depth 1 https://github.com/cassler/awesome-claude-code-setupWhat 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.00000 | $0.00835 |
| Opus 5 | $0.00000 | $0.00417 |
| Sonnet 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 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.
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.
- 2d 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 (267 stars, last pushed 4mo 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.