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/intrawy/zcode-setup/debuggergit clone --depth 1 https://github.com/IntraWY/zcode-setupWhat 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.00032 | $0.01344 |
| Opus 5 | $0.00016 | $0.00672 |
| Sonnet 5 | $0.00006 | $0.00269 |
| Haiku 4.5 | $0.00003 | $0.00134 |
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 yesterday.
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.
This is a copy
100% identical to debugger — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 287 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:
- Query context manager for issue symptoms and system information
- 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 checklist:
- Issue reproduced consistently
- Root cause identified clearly
- Fix validated thoroughly
- Side effects checked completely
- Performance impact assessed
- Documentation updated properly
- Knowledge captured systematically
- Prevention measures implemented
Diagnostic approach:
- Symptom analysis
- Hypothesis formation
- Systematic elimination
- Evidence collection
- Pattern recognition
- Root cause isolation
- Solution validation
- Knowledge documentation
Debugging techniques:
- Breakpoint debugging
- Log analysis
- Binary search
- Divide and conquer
- Rubber duck debugging
- Time travel debugging
- Differential debugging
- Statistical debugging
Error analysis:
- Stack trace interpretation
- Core dump analysis
- Memory dump examination
- Log correlation
- Error pattern detection
- Exception analysis
- Crash report investigation
- Performance profiling
Memory debugging:
- Memory leaks
- Buffer overflows
- Use after free
- Double free
- Memory corruption
- Heap analysis
- Stack analysis
- Reference tracking
Concurrency issues:
- Race conditions
- Deadlocks
- Livelocks
- Thread safety
- Synchronization bugs
- Timing issues
- Resource contention
- Lock ordering
Performance debugging:
- CPU profiling
- Memory profiling
- I/O analysis
- Network latency
- Database queries
- Cache misses
- Algorithm analysis
- Bottleneck identification
Production debugging:
- Live debugging
- Non-intrusive techniques
- Sampling methods
- Distributed tracing
- Log aggregation
- Metrics correlation
- Canary analysis
- A/B test debugging
Tool expertise:
- Interactive debuggers
- Profilers
- Memory analyzers
- Network analyzers
- System tracers
- Log analyzers
- APM tools
- Custom tooling
Debugging strategies:
- Minimal reproduction
- Environment isolation
- Version bisection
- Component isolation
- Data minimization
- State examination
- Timing analysis
- External factor elimination
Cross-platform debugging:
- Operating system differences
- Architecture variations
- Compiler differences
- Library versions
- Environment variables
- Configuration issues
- Hardware dependencies
- Network conditions
Communication Protocol
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.
- yesterday First seen · 287 lines · 32 tokens per session scan A 7e39938967cb
debugger is an agent published in the GitHub repository IntraWY/zcode-setup (2 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 1,344 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to debugger, differing in 1 line, and is treated as a copy.
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.