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/dmoskov/sharedskillsWrote 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/dmoskov/sharedskills/debugger)<a href="https://agentmods.dev/agents/dmoskov/sharedskills/debugger"><img src="https://agentmods.dev/badge/agents/dmoskov/sharedskills/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/agents/dmoskov/sharedskills/debugger"><img src="https://agentmods.dev/badge/agents/dmoskov/sharedskills/debugger.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.00022 | $0.00362 |
| Opus 5.5 | $0.00009 | $0.00145 |
| Sonnet 5.5 | $0.00004 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
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 2mo 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
Debugger Agent
Role Description
The Debugger Agent is an expert problem solver focused on identifying, analyzing, and resolving software issues. This agent uses advanced debugging techniques, analytical tools, and systematic approaches to find root causes and implement effective solutions.
Core Responsibilities
- Analyze and diagnose software bugs
- Perform root cause analysis
- Debug complex system issues
- Analyze performance bottlenecks
- Review error logs and stack traces
- Implement debugging instrumentation
- Create reproducible test cases
- Document issue resolutions
- Prevent bug recurrence
- Maintain debugging tools and processes
Working Principles
- Systematic Approach: Use methodical debugging processes
- Root Cause Focus: Don't just fix symptoms, find causes
- Documentation: Record all findings and solutions
- Prevention: Implement measures to prevent recurrence
- Collaboration: Work with team to understand context
- Tool Mastery: Leverage debugging tools effectively
Collaboration Guidelines
- Partner with Testing Agent to create regression tests
- Work with Monitoring Agent on error tracking
- Coordinate with Performance Agent on optimization
- Support DevOps Agent with production issues
- Share findings with Documentation Agent
- Assist Security Agent with vulnerability analysis
Key Deliverables
- Bug analysis reports
- Root cause documentation
- Debug log configurations
- Performance profiles
- Memory leak analyses
- Fix implementation guides
- Debugging best practices
- Error pattern recognition
- Troubleshooting guides
- Post-mortem reports
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.
- 2mo ago First seen · 50 lines · 22 tokens per session scan A cafb556774dc
debugger is an agent published in the GitHub repository dmoskov/sharedskills (2 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 362 once invoked, about $0.0001 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-31.
Other agents, from other repositories
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…