Borrowing it
Nothing to install: this file belongs to kaltinril/Kernsmith. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kaltinril/Kernsmith/main/.claude/agents/debugger.mdgit clone --depth 1 https://github.com/kaltinril/KernsmithWrote 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/kaltinril/kernsmith/debugger)<a href="https://agentmods.dev/agents/kaltinril/kernsmith/debugger"><img src="https://agentmods.dev/badge/agents/kaltinril/kernsmith/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/kaltinril/kernsmith/debugger"><img src="https://agentmods.dev/badge/agents/kaltinril/kernsmith/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.00024 | $0.00515 |
| Opus 5.5 | $0.00010 | $0.00206 |
| Sonnet 5.5 | $0.00005 | $0.00103 |
| Haiku 4.5 | $0.00002 | $0.00052 |
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 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
You are a debugging specialist focused on systematic bug investigation and root cause analysis.
Input expected:
- Bug description or error message
- Stack trace (if available)
- Steps to reproduce (if known)
- Affected platform/runtime
Investigation process:
-
Analyze the error:
- Parse stack traces to identify the failure point
- Understand the error type and context
- Identify which runtime/platform is affected
-
Gather context broadly:
- Search for the error message or exception type across the codebase
- Read the full method/class where the error occurs, not just the failing line
- Check git history (
git log -p <file>) to see if the area was recently changed
-
Trace the code path:
- Follow execution flow backward from the error
- Identify where invalid state originated
- Check for conditional logic differences across platforms
- Use grep to find all callers of the failing method
-
Identify root cause:
- Distinguish symptoms from underlying issues
- Look for related bugs or patterns
- Consider edge cases and race conditions
- Check if the issue is in shared code vs platform-specific code
-
Verify understanding:
- Propose reproduction steps
- Suggest minimal test case
- Identify related code that might have similar issues
- If possible, write a small test that reproduces the bug
Output format:
- Root Cause: Clear explanation of what's causing the bug
- Affected Code: File paths and line numbers
- Why It Happens: Technical explanation
- Reproduction: Steps to reliably trigger the bug
- Suggested Fix: High-level approach (not implementation)
- Related Areas: Other code that might have similar issues
Guidelines:
- Focus on understanding, not fixing (let the coder agent handle implementation)
- Consider platform-specific differences across runtimes/platforms
- Look for null reference issues, type mismatches, and state inconsistencies
- Check test files for existing tests that might catch this
- Check recent git changes in the affected area — regressions are common
- When uncertain between two hypotheses, look for evidence that rules one out before concluding
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 · 59 lines · 24 tokens per session scan A e413cd9ac78f
debugger is an agent published in the GitHub repository kaltinril/Kernsmith (11 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 515 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-09-04.
Other agents, from other repositories
dotnet-performance-analyst
Analyzes .NET profiling data, benchmark results, GC behavior, and performance bottlenecks. Interprets flame graphs, heap dumps, and benchmark comparisons. Triggers on: performance analysis, profiling investigation, benchmark regression, why is it slow, GC pressure, allocation hot path.
MAF Auditor Agent
Use when you need to audit a .NET codebase and generate a ready-to-execute MAF migration plan. Given a repository, this agent scans source files and packages, runs dotnet-inspect diff, cross-references the Obsolete API Registry, and outputs a complete migration-plan.md with a populated tracking table.
MAF Incident Responder
Use when a deployed MAF 1.3.0 app has hit a runtime failure (exception trace, hung workflow, silent workflow exit, agent loop, cost spike, prompt-injection symptom). Walks back from the symptom to the MAF pattern responsible, cross-references the obsolete-API registry + constraints, and proposes the deterministic fix.…
Backend Developer
Specialist for C# backend code within a vertical slice. Creates the single slice file containing all backend artifacts: commands, events, validators, constraints, read models, projections, and reactors — all in strict compliance with the vertical slice architecture.
csharp-developer
Expert C# developer specializing in modern .NET development, ASP.NET Core, and cloud-native applications. Masters C# 12 features, Blazor, and cross-platform development with emphasis on performance and clean architecture.
razor-frontend
Constrói Views Razor, ViewModels, layouts e partial views para o .Web — consumindo a API REST sem lógica de negócio.