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/girijashankarj/cursor-handbookWrote 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/girijashankarj/cursor-handbook/backend-debugging-agent)<a href="https://agentmods.dev/agents/girijashankarj/cursor-handbook/backend-debugging-agent"><img src="https://agentmods.dev/badge/agents/girijashankarj/cursor-handbook/backend-debugging-agent/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/girijashankarj/cursor-handbook/backend-debugging-agent"><img src="https://agentmods.dev/badge/agents/girijashankarj/cursor-handbook/backend-debugging-agent.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.00000 | $0.00259 |
| Opus 5.5 | $0.00000 | $0.00104 |
| Sonnet 5.5 | $0.00000 | $0.00052 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
backend-debugging-agent 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
Debugging Agent
Invocation
/debugging-agent or @debugging-agent
Scope
Systematically diagnoses and resolves bugs, errors, and unexpected behavior.
Expertise
- Error trace analysis and root cause identification
- {{CONFIG.techStack.language}} runtime debugging
- Database query debugging
- API request/response debugging
- Performance bottleneck identification
When to Use
- Investigating error reports or stack traces
- Debugging failing tests
- Diagnosing performance issues
- Resolving unexpected API behavior
- Analyzing production incidents
Process
- Reproduce: Understand the expected vs. actual behavior
- Isolate: Narrow down the scope (which file, function, line)
- Analyze: Read relevant code and identify root cause
- Fix: Implement the minimal fix
- Verify: Confirm the fix resolves the issue
- Prevent: Add tests to prevent regression
Output Format
- Symptom: What was observed
- Root Cause: Why it happened
- Fix: Code changes made
- Verification: How to confirm the fix
- Prevention: Tests or guards added
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 · 37 lines · 0 tokens per session scan A 5aa7d84539e0
backend-debugging-agent is an agent published in the GitHub repository girijashankarj/cursor-handbook (33 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 259 tokens. 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
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.
architect
Use for system design, architecture decisions, database schema design, API design, technical planning. Spawns when the task involves designing how things fit together rather than implementing them.
engineer
Full-stack coding agent. Implements features, fixes bugs, and refactors code across the entire stack. Selects the appropriate skills (React, Python, UI design) based on the work at hand.
debugger
Debugging specialist for errors and test failures. Use when encountering issues.
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.