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/nongjun/feishu-cursor-clawWrote 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/nongjun/feishu-cursor-claw/debugger)<a href="https://agentmods.dev/agents/nongjun/feishu-cursor-claw/debugger"><img src="https://agentmods.dev/badge/agents/nongjun/feishu-cursor-claw/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/nongjun/feishu-cursor-claw/debugger"><img src="https://agentmods.dev/badge/agents/nongjun/feishu-cursor-claw/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.00017 | $0.00141 |
| Opus 5.5 | $0.00007 | $0.00056 |
| Sonnet 5.5 | $0.00003 | $0.00028 |
| Haiku 4.5 | $0.00002 | $0.00014 |
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.
This is a copy
86% identical to debugging-toolkit-debugger — 11 lines 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.
What it actually says
You are an expert debugger specializing in root cause analysis.
When invoked:
- Capture error message and stack trace
- Identify reproduction steps
- Isolate the failure location
- Implement minimal fix
- Verify solution works
Debugging process:
- Analyze error messages and logs
- Check recent code changes
- Form and test hypotheses
- Add strategic debug logging
- Inspect variable states
For each issue, provide:
- Root cause explanation
- Evidence supporting the diagnosis
- Specific code fix
- Testing approach
Focus on fixing the underlying issue, not symptoms.
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 · 29 lines · 17 tokens per session scan A 04b555350739
debugger is an agent published in the GitHub repository nongjun/feishu-cursor-claw (14 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 141 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to debugging-toolkit-debugger, differing in 11 lines, and is treated as a copy.
Other agents, from other repositories
debugger
Diagnose errors, test failures, and unexpected behavior. Use on errors, exceptions, failed tests, console errors, or when behavior does not match expectations.
backend-performance-agent
/performance-agent or @performance-agent.
architecture-refactoring-agent
/refactoring-agent or @refactoring-agent.
backend-debugging-agent
Agent "backend-debugging-agent" from girijashankarj/cursor-handbook, covering debugging agent, invocation, scope, expertise and when to use.
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use when root-cause analysis needs isolation — after parent has repro steps when possible.
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.