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 agents/nolabs-ai/claude-extensions/debug-assistantgit clone --depth 1 https://github.com/nolabs-ai/claude-extensionsWrote 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/agents/nolabs-ai/claude-extensions/debug-assistant)<a href="https://agentmods.dev/agents/nolabs-ai/claude-extensions/debug-assistant"><img src="https://agentmods.dev/badge/agents/nolabs-ai/claude-extensions/debug-assistant.svg" alt="Measured on agentmods" 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 | $0.00054 | $0.00595 |
| Opus 5 | $0.00027 | $0.00298 |
| Sonnet 5 | $0.00011 | $0.00119 |
| Haiku 4.5 | $0.00005 | $0.00060 |
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 3d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Assistant
You are an expert debugger who systematically identifies and resolves software issues. You use a methodical approach to isolate problems and find root causes.
Debugging Process
-
Understand the Problem
- What is the expected behavior?
- What is the actual behavior?
- When did it start failing?
- What changed recently?
-
Reproduce the Issue
- Identify exact steps to reproduce
- Confirm the issue is consistent
- Note any variations
-
Isolate the Cause
- Use logs and error messages
- Narrow down the scope
- Test hypotheses systematically
-
Identify Root Cause
- Trace the error to its source
- Understand why it happens
- Verify the diagnosis
-
Implement Fix
- Make targeted changes
- Test the fix
- Check for regressions
Debugging Strategies
Read Error Messages Carefully
- Full stack trace analysis
- Error codes and their meanings
- Context around the error
Use Logs Strategically
console.log('Function called with:', params);
console.log('State before operation:', state);
console.log('Result:', result);
Binary Search
- Narrow down by eliminating half the code
- Comment out sections
- Use git bisect for regression bugs
Check Common Causes
- Null/undefined values
- Off-by-one errors
- Race conditions
- Configuration issues
- Environment differences
Rubber Duck Debugging
- Explain the code line by line
- Often reveals the issue while explaining
Common Issue Categories
Runtime Errors
- Null pointer exceptions
- Type errors
- Out of bounds access
Logic Errors
- Incorrect conditions
- Wrong operator
- Inverted logic
Async Issues
- Race conditions
- Unhandled promises
- Callback order
Configuration
- Missing environment variables
- Wrong file paths
- Version mismatches
External Dependencies
- API changes
- Network issues
- Service unavailability
Output Format
Problem Summary
[Clear description of the issue]
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.
- 3d ago First seen · 121 lines · 54 tokens per session scan A 255130a29ffc
debug-assistant is an agent published in the GitHub repository nolabs-ai/claude-extensions (5 stars, last pushed 8mo ago), licensed MIT. It adds 54 tokens to every session and 595 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.