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/rafaelkamimura/claude-toolsWrote 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/rafaelkamimura/claude-tools/debug-assistant)<a href="https://agentmods.dev/commands/rafaelkamimura/claude-tools/debug-assistant"><img src="https://agentmods.dev/badge/commands/rafaelkamimura/claude-tools/debug-assistant/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/rafaelkamimura/claude-tools/debug-assistant"><img src="https://agentmods.dev/badge/commands/rafaelkamimura/claude-tools/debug-assistant.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.02374 |
| Opus 5.5 | $0.00000 | $0.00950 |
| Sonnet 5.5 | $0.00000 | $0.00475 |
| Haiku 4.5 | $0.00000 | $0.00237 |
Grade A, and why
debug-assistant 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 — 423 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intelligent Debugging Helper
Advanced debugging assistant that analyzes errors, suggests fixes, traces root causes, and sets up debugging environments.
Purpose
- Analyze error logs and stack traces
- Suggest fixes based on error patterns
- Set up debugging environments
- Generate reproduction steps
- Track down root causes with specialized agents
Workflow
Step 1: Error Input
-
STOP → "How would you like to provide the error?"
1. Paste error message/stack trace 2. Point to log file 3. Describe the issue 4. Run failing command 5. Analyze recent crashes Choose method (1-5): -
Context Gathering
- STOP → "When did this error start? (timestamp/commit/today):"
- STOP → "Is it reproducible? (always/sometimes/once):"
- STOP → "What were you doing when it occurred?:"
Step 2: Error Analysis
-
Parse Error Information
// Extract key information const errorInfo = { type: "TypeError", message: "Cannot read property 'x' of undefined", file: "src/components/UserList.jsx", line: 45, column: 12, stack: [...], timestamp: "2024-01-15T10:30:00Z" }; -
Categorize Error Type
error_categories: - Runtime Errors: - TypeError - ReferenceError - RangeError - Async Errors: - Promise rejection - Callback errors - Race conditions - Network Errors: - Connection refused - Timeout - CORS issues - Build Errors: - Compilation failure - Module not found - Syntax errors -
Deploy Analysis Agents
- debugger: Deep error analysis
- backend-architect: System-level debugging
- test-automator: Create reproduction test
- performance-engineer: Performance-related issues
Step 3: Root Cause Analysis
- Trace Error Source
# Git blame to find when introduced git blame -L 40,50 src/components/UserList.jsx # Check recent changes git log -p --since="2 days ago" src/components/UserList.jsx
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 · 423 lines · 0 tokens per session scan A 9b65ed08bf9c
debug-assistant is a command published in the GitHub repository rafaelkamimura/claude-tools (10 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,374 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-31.
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.
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.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
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.