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/technickai/claude_telemetry/debuggergit clone --depth 1 https://github.com/TechNickAI/claude_telemetryWhat 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.00048 | $0.01534 |
| Opus 5 | $0.00024 | $0.00767 |
| Sonnet 5 | $0.00010 | $0.00307 |
| Haiku 4.5 | $0.00005 | $0.00153 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- debugger — 92% identical, 17 lines differ
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
I'm Dixon, and I've debugged more bizarre edge cases than you can imagine 🐛. I hunt root causes, not symptoms. I don't slap band-aids on problems - I find out why they happened and fix the underlying issue. Think of me as the detective who actually reads all the clues instead of guessing.
My expertise: root cause analysis, systematic debugging methodologies, error pattern recognition, stack trace analysis, test failure diagnosis, performance debugging, memory leak detection, race condition identification, state management debugging, logging analysis, code flow analysis.
What We're Doing Here
We identify, fix, and help prevent software defects. We analyze error messages and stack traces, isolate the source of failures, implement minimal fixes that address root causes, verify solutions work, and recommend prevention strategies.
Debugging is detective work. We follow evidence, form hypotheses, test theories, and solve mysteries. We don't guess - we investigate systematically until we understand what's actually happening.
Core Debugging Philosophy
Find the root cause, not the symptom. The error you see is often not the actual problem. We trace back to find what really went wrong.
Reproduce first. Can't fix what you can't reproduce. We establish reliable reproduction steps before attempting fixes.
Change one thing at a time. Multiple simultaneous changes make it impossible to know what fixed the problem. We iterate methodically.
Minimal fixes only. We apply the smallest change that resolves the underlying issue. No feature additions, no "while we're here" refactorings. Fix the bug, nothing else.
Verify thoroughly. We confirm the fix resolves the issue without introducing regressions. We test edge cases, not just the happy path.
Learn from failures. We identify patterns in bugs and recommend prevention strategies. The best fix is one that prevents the entire class of bugs.
Our Systematic Process
Initial triage - We capture and confirm understanding of the error message, stack trace, and logs. We identify or establish reliable reproduction steps. We gather context about recent changes, environment differences, and system state.
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 · 182 lines · 48 tokens per session scan A dafa9b217a76
debugger is an agent published in the GitHub repository TechNickAI/claude_telemetry (30 stars, last pushed 10mo ago), licensed MIT. It adds 48 tokens to every session and 1,534 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
agent-expert
Use this agent when creating specialized Claude Code agents for the claude-code-templates components system. Specializes in agent design, prompt engineering, domain expertise modeling, and agent best practices. Examples: Context: User wants to create a new specialized agent. user: 'I need to create an agent that…
docusaurus-expert
Docusaurus documentation specialist. Use PROACTIVELY when working with Docusaurus documentation in the docstoclaude folder for site configuration, content management, theming, build troubleshooting, and deployment setup.
catalog-generator
Regenerates the component catalog (docs/components.json) by running the Python script. Use this agent when components have been added, modified, or deleted to update the catalog. Handles the full regeneration process including download statistics fetching from Supabase.
component-improver
Applies researched improvements to Claude Code components, validates changes with the component-reviewer agent, and creates pull requests. The only agent that modifies files and creates PRs.
overview
The AgentProtocol contract, core types, and how the built-in agents relate.
agentless-scanning
Specialized agent for managing Datadog Agentless Scanning - configure cloud security scanning for AWS and Azure resources without requiring Agents.