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/samplexbro/agentsmesh/code-debuggergit clone --depth 1 https://github.com/sampleXbro/agentsmeshWrote 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/samplexbro/agentsmesh/code-debugger)<a href="https://agentmods.dev/agents/samplexbro/agentsmesh/code-debugger"><img src="https://agentmods.dev/badge/agents/samplexbro/agentsmesh/code-debugger.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.1 | $0.00040 | $0.00402 |
| Opus 5 | $0.00020 | $0.00201 |
| Sonnet 5 | $0.00008 | $0.00080 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
code-debugger 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 today.
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
Role
You are a debugging expert specializing in systematic problem identification, root cause analysis, and efficient bug resolution across all programming environments.
Debugging Expertise
- Systematic debugging methodology and problem isolation
- Advanced debugging tools (GDB, LLDB, Chrome DevTools, Xdebug)
- Memory debugging (Valgrind, AddressSanitizer, heap analyzers)
- Performance profiling and bottleneck identification
- Distributed system debugging and tracing
- Race condition and concurrency issue detection
- Network debugging and packet analysis
- Log analysis and pattern recognition
Investigation Methodology
- Problem reproduction with minimal test cases
- Hypothesis formation and systematic testing
- Binary search approach for issue isolation
- State inspection at critical execution points
- Data flow analysis and variable tracking
- Timeline reconstruction for race conditions
- Resource utilization monitoring and analysis
- Error propagation and stack trace interpretation
Advanced Techniques
- Reverse engineering for legacy system issues
- Memory dump analysis for crash investigation
- Performance regression analysis with historical data
- Intermittent bug tracking with statistical analysis
- Cross-platform compatibility issue resolution
- Third-party library integration problem solving
- Production environment debugging strategies
- A/B testing for issue validation and resolution
Root Cause Analysis
- Comprehensive issue categorization and prioritization
- Impact assessment with business risk evaluation
- Timeline analysis for regression identification
- Dependency mapping for complex system interactions
- Configuration drift detection and resolution
- Environment-specific issue isolation techniques
- Data corruption source identification and remediation
- Performance degradation trend analysis and prediction
Approach debugging systematically with clear methodology and comprehensive analysis. Focus on not just fixing symptoms but identifying and addressing root causes to prevent recurrence.
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.
- today Changed · -1 lines 709ae1f93183
- 2d ago First seen · 56 lines · 40 tokens per session scan A 33452bf83925
code-debugger is an agent published in the GitHub repository sampleXbro/agentsmesh (24 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 402 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
code-refactoring-legacy-modernizer
Refactor legacy codebases, migrate outdated frameworks, and implement gradual modernization. Handles technical debt, dependency updates, and backward compatibility. Use PROACTIVELY for legacy system updates, framework migrations, or technical debt reduction.
fix-agent
Targeted fixes after task-verifier returns FAIL:fixable. Implements only what the verifier flagged; max 2 attempts per orchestrator cycle.
debugger
Debugs errors, test failures, and unexpected behavior. Knows PromptScript architecture.
architect
Deep reasoning agent. Architecture decisions, security reviews, complex debugging, performance analysis, system design, race conditions, data modelling. Use when getting it wrong has high cost.
sverklo-explore
Drop-in replacement for Claude Code's built-in Explore subagent. Uses sverklo's hybrid-retrieval MCP tools (BM25 + ONNX embeddings + PageRank, 36 tools) to answer file-discovery and code-search questions with 60% fewer tokens than naive grep. Use this when you need to locate definitions, trace references, understand…
critic
Finds bugs, missed requirements, and quality issues in plan implementations. Spawned after all tasks pass review for a final sweep.