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 skills add sampleXbro/agentsmesh --skill am-agent-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/skills/samplexbro/agentsmesh/am-agent-code-debugger)<a href="https://agentmods.dev/skills/samplexbro/agentsmesh/am-agent-code-debugger"><img src="https://agentmods.dev/badge/skills/samplexbro/agentsmesh/am-agent-code-debugger/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/skills/samplexbro/agentsmesh/am-agent-code-debugger"><img src="https://agentmods.dev/badge/skills/samplexbro/agentsmesh/am-agent-code-debugger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00042 | $0.00426 |
| Opus 5.5 | $0.00017 | $0.00170 |
| Sonnet 5.5 | $0.00008 | $0.00085 |
| Haiku 4.5 | $0.00004 | $0.00043 |
Grade A, and why
am-agent-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 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.
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.
- 1mo ago First seen · 57 lines · 42 tokens per session scan A 18b6e6f75b7d
am-agent-code-debugger is a skill published in the GitHub repository sampleXbro/agentsmesh (25 stars, last pushed 21d ago), licensed MIT. It adds 42 tokens to every session and 426 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
parallel-investigation
Coordinates parallel investigation threads to simultaneously explore multiple hypotheses or root causes across different system areas. Use when debugging production incidents, slow API performance, multi-system integration failures, or complex bugs where the root cause is unclear and multiple plausible theories exist…
hypothesis-testing
Applies the scientific method to debugging by helping users form specific, testable hypotheses, design targeted experiments, and systematically confirm or reject theories to find root causes. Use when a user says their code isn't working, they're getting an error, something broke, they want to troubleshoot a bug, or…
trace-and-isolate
Applies systematic tracing and isolation techniques to pinpoint exactly where a bug originates in code. Use when a bug is hard to locate, code is not working as expected, an error or crash appears with unclear cause, a regression was introduced between recent commits, or you need to narrow down which component…
root-cause-analysis
Performs systematic root cause analysis to identify the true source of bugs, errors, and unexpected behavior through structured investigation phases — not just treating symptoms. Use when a user reports a bug, crash, error, or broken behavior and needs to debug, troubleshoot, or investigate why something is not…
systematic-debugging
4-phase debugging protocol for diagnosing and fixing failing tests.
tables-error-sweep
Clay tables — sweep a table for errored rows and report grouped by root cause (not a specific record). Use when the user asks "what's erroring in {table}?", "show failed rows", or "is {action} failing?".