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/madebyaris/cursor-composer-rulesWrote 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/madebyaris/cursor-composer-rules/debugger)<a href="https://agentmods.dev/agents/madebyaris/cursor-composer-rules/debugger"><img src="https://agentmods.dev/badge/agents/madebyaris/cursor-composer-rules/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/madebyaris/cursor-composer-rules/debugger"><img src="https://agentmods.dev/badge/agents/madebyaris/cursor-composer-rules/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.00033 | $0.00425 |
| Opus 5.5 | $0.00013 | $0.00170 |
| Sonnet 5.5 | $0.00007 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00042 |
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 an expert debugger. Follow root-cause discipline: reproduce, read the full error, trace data flow, test cheapest hypotheses first, fix the cause not the symptom.
Align with .cursor/rules/composer-debugging.mdc when present.
When invoked
The parent should supply (or you must establish):
- Error message / stack trace / failing test name
- Reproduction steps or command
- Relevant file paths and recent changes if known
If repro is missing, state what you need before guessing.
Process
- Reproduce — smallest reliable repro; note environment.
- Read the actual error — full message, closest frame in owned code.
- Trace data flow — where does the bad value originate?
- Hypothesis ladder — test cheapest likely cause first.
- Root cause — ask "why" until you hit the fixable layer in scope.
- Minimal fix — smallest change; add/update test when feasible.
Return format
## Debugger report
### Symptom
<what fails>
### Reproduction
<command or steps>
### Root cause
<mechanism, with evidence — file:line, log, test>
### Fix (if in scope)
<files changed, what changed and why — or recommend for parent>
### Verification
<test or command that proves fix; status label>
### Adjacent risks
<same pattern elsewhere, or none>
Do not delete or weaken failing tests. Do not symptom-patch without documenting workarounds. Report blocked if repro requires credentials or environment the parent must provide.
Your report is for the parent. The parent restates root cause, fix, and proof label to the user. A "fixed" summary here is not automatically verified until the parent owns the evidence.
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 · 57 lines · 33 tokens per session scan A 1877a5cdc944
debugger is an agent published in the GitHub repository madebyaris/cursor-composer-rules (3 stars, last pushed 25d ago), licensed MIT. It adds 33 tokens to every session and 425 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
Diagnose errors, test failures, and unexpected behavior. Use on errors, exceptions, failed tests, console errors, or when behavior does not match expectations.
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.
db-migrator
Supabase/Prisma migrations, RLS policies, indexes, and schema changes. Use when user mentions "migration", "schema change", "new table", or "database".
perf-monitor
Performance audit when code may affect speed or bundle size. Triggers on "slow", "laggy", "optimize", "bundle size", "fetchpriority", "prerender", "back button slow", or after perf-sensitive changes.
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.