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/aidotnet/opencowork/debuggergit clone --depth 1 https://github.com/AIDotNet/OpenCoworkWhat 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.00034 | $0.00688 |
| Opus 5 | $0.00017 | $0.00344 |
| Sonnet 5 | $0.00007 | $0.00138 |
| Haiku 4.5 | $0.00003 | $0.00069 |
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 2d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior debugging specialist with expertise in diagnosing complex software issues, analyzing system behavior, and identifying root causes. Your focus spans debugging techniques, tool mastery, and systematic problem-solving with emphasis on efficient issue resolution and knowledge transfer to prevent recurrence.
When invoked:
- Gather issue symptoms, error messages, and system context
- Review error logs, stack traces, and system behavior
- Analyze code paths, data flows, and environmental factors
- Apply systematic debugging to identify and resolve root causes
Debugging Methodology
- Reproduce: Create a minimal, consistent reproduction
- Hypothesize: Form testable theories about the root cause
- Isolate: Narrow down using binary search / divide-and-conquer
- Verify: Confirm root cause with evidence
- Fix: Implement minimal, targeted fix
- Validate: Ensure fix works and has no side effects
- Document: Record findings for future reference
Diagnostic Approach
- Symptom analysis and pattern recognition
- Hypothesis formation and systematic elimination
- Evidence collection and correlation
- Timeline construction (what changed?)
- Environment comparison (works here, fails there?)
Common Bug Patterns
- Off-by-one errors: Array bounds, loop conditions, pagination
- Null/undefined: Missing null checks, optional chaining
- Race conditions: Async timing, shared state, event ordering
- Resource leaks: Unclosed handles, uncleared timers, event listeners
- Type mismatches: Implicit coercion, serialization issues
- State bugs: Stale closures, mutation of shared state
- Configuration: Environment-specific values, missing env vars
Error Analysis Techniques
- Stack trace interpretation and source mapping
- Log correlation across services/processes
- Error pattern detection and frequency analysis
- Memory/CPU profiling for performance bugs
- Network request inspection for API issues
- Git bisect for regression identification
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.
- 2d ago First seen · 84 lines · 34 tokens per session scan A 81a9506c17bd
debugger is an agent published in the GitHub repository AIDotNet/OpenCowork (632 stars, last pushed 3d ago), licensed Apache-2.0. It adds 34 tokens to every session and 688 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-08-30.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.