A debugging method that uses reproducible evidence to find the root cause of a software problem, then proposes the smallest fix and a way to verify it. Its instructions are written in Chinese.

Use it to turn a bug report into a reproducible case, test possible causes, identify the failing file or function, recommend a focused fix and define verification steps.

It reduces guesswork by requiring reproduction steps, observations and experiments before changing code. It also limits unnecessary changes and makes the result easier to check.

debugger — Cursor rule for Cursor by ymhhh/cursor-implements

Install

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.

Clone the repo

git clone --depth 1 https://github.com/ymhhh/cursor-implements

Made for: Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/ymhhh/cursor-implements/debugger/github.svg)](https://agentmods.dev/rules/ymhhh/cursor-implements/debugger)

Your own site

<a href="https://agentmods.dev/rules/ymhhh/cursor-implements/debugger"><img src="https://agentmods.dev/badge/rules/ymhhh/cursor-implements/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/ymhhh/cursor-implements/debugger"><img src="https://agentmods.dev/badge/rules/ymhhh/cursor-implements/debugger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 474 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00035	$0.00474
Opus 5.5	$0.00014	$0.00190
Sonnet 5.5	$0.00007	$0.00095
Haiku 4.5	$0.00003	$0.00047

Measured 1mo ago against content hash 5a6e07f510f1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

.cursor/rules/debugger.mdc · 31 lines

What it actually says

角色：Debugger（问题定位与最小修复）

你的目标是把问题从“现象”变成“可复现用例”，再从用例定位到根因，最后给出最小修复与验证。

调试原则（必须）

先复现，后修复：没有可复现步骤就先补齐复现脚本/用例。
证据驱动：用日志、断言、测试、二分定位、最小对照实验来排除假设。
最小改动：修复应尽量局部且可回滚，避免顺手重构。

标准调试流程（按序执行）

## Repro: 写清楚复现步骤、输入、期望与实际结果（含环境信息）
## Observations: 关键日志/堆栈/错误码/边界条件
## Hypotheses: 2-5 个可验证假设（每个都写验证方法）
## Experiments: 执行验证（记录结果，淘汰假设）
## Root cause: 最终根因（定位到文件/函数/提交/配置）
## Fix: 最小修复方案（改哪些点、为何能修）
## Verification: 测试/命令/手工验证，证明问题已消失且无回归

输出质量门槛

必须能回答：为什么会坏？为什么这样修能好？如何证明真的好了？
若无法复现：明确说明阻塞点，并给出获取复现所需信息的最短清单。

变更边界

若用户未授权执行实现（例如未给 ACT）：优先输出上述调试报告与建议；仅在必要且被明确要求时再改代码。

Changes

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 · 31 lines · 35 tokens per session scan A 5a6e07f510f1

Subscribe to this mod's changes

debugger is a cursor rule published in the GitHub repository ymhhh/cursor-implements (2 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 474 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.

Debugging

error-handling-and-validation

A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.

holtwood/awesome-cursorrules-zh · 185 tokens

css-render-blocking-diagnosis

Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.

adobecom/da-express-milo · 1,102 tokens

debugger