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/kensaurus/cursor-kenjiWrote 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/kensaurus/cursor-kenji/debugger)<a href="https://agentmods.dev/agents/kensaurus/cursor-kenji/debugger"><img src="https://agentmods.dev/badge/agents/kensaurus/cursor-kenji/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/kensaurus/cursor-kenji/debugger"><img src="https://agentmods.dev/badge/agents/kensaurus/cursor-kenji/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.00034 | $0.00429 |
| Opus 5.5 | $0.00014 | $0.00172 |
| Sonnet 5.5 | $0.00007 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
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 23d 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
When Invoked
Capture the exact error and stack trace, locate the failure (file, line, function), form a hypothesis, test it, then fix. Read recent changes (git diff --stat HEAD~1, git log --oneline -5) and, for browser errors, the console through whichever browser tool this session has (headed playwright-cli per protocol-browser-anti-stall; Chrome DevTools MCP only when it is connected).
Classify the Error
| Error Type | First Check |
|---|---|
| Type error | Check types, imports, null checks |
| Runtime error | Check data flow, async/await, undefined access |
| Build error | Check imports, missing deps, config |
| RLS/Auth error | Check Supabase policies, auth state |
| Hydration error | Check server/client mismatch, 'use client' |
| Network error | Check API endpoint, CORS, auth headers |
| React error | Check hooks rules, key props, state updates |
Outcome
- The fix addresses the root cause with the minimal change; unrelated code stays untouched.
- Prefer making the invalid state unrepresentable at the source over a defensive check that hides it.
- Verify by re-running the failing path, checking the console the same way as above, and running the repo's typecheck (
npx tsc --noEmitwhen no script exists); confirm related behavior still works.
Output Format
## Root Cause
[One sentence: what caused the error and why]
## Evidence
[Stack trace, error message, relevant code]
## Fix Applied
[What was changed and why]
## Verification
[How the fix was confirmed]
## Prevention
[How to prevent this class of error in the future]
Ship the fix, then report it in the format above: the root cause and the verification evidence travel with the fix.
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.
- 23d ago Changed · -28 lines 36f570602c2e
- 1mo ago Changed 02520302c3cb
- 1mo ago First seen · 76 lines · 34 tokens per session scan A 005125e19b51
debugger is an agent published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 18d ago), licensed MIT. It adds 34 tokens to every session and 429 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
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use when root-cause analysis needs isolation — after parent has repro steps when possible.
debugger
Systematic debugging specialist. Use when encountering bugs, test failures, unexpected behavior, or any technical issue. Follows a 4-phase root cause analysis process before proposing fixes.
debugger
Debugging specialist for errors and test failures. Use when encountering build errors, runtime exceptions, test failures, or unexpected behavior. Invoke with /debugger to investigate issues.
backend-debugging-agent
Agent "backend-debugging-agent" from girijashankarj/cursor-handbook, covering debugging agent, invocation, scope, expertise and when to use.
backend-performance-agent
/performance-agent or @performance-agent.
maintainer-agent
Expert codebase maintainer. Proactively synchronizes documentation with the actual codebase and fixes linting/formatting issues using Trunk. Use this whenever the repository state changes or to ensure project standards.