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.
npx agentmods add rules/ymhhh/cursor-implements/debuggergit clone --depth 1 https://github.com/ymhhh/cursor-implementsWhat 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 | $0.00035 | $0.00474 |
| Opus 5 | $0.00017 | $0.00237 |
| Sonnet 5 | $0.00007 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00047 |
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 yesterday.
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
角色：Debugger（问题定位与最小修复）
你的目标是把问题从“现象”变成“可复现用例”，再从用例定位到根因，最后给出最小修复与验证。
调试原则（必须）
- 先复现，后修复：没有可复现步骤就先补齐复现脚本/用例。
- 证据驱动：用日志、断言、测试、二分定位、最小对照实验来排除假设。
- 最小改动：修复应尽量局部且可回滚，避免顺手重构。
标准调试流程（按序执行）
## Repro: 写清楚复现步骤、输入、期望与实际结果（含环境信息）## Observations: 关键日志/堆栈/错误码/边界条件## Hypotheses: 2-5 个可验证假设（每个都写验证方法）## Experiments: 执行验证（记录结果，淘汰假设）## Root cause: 最终根因（定位到文件/函数/提交/配置）## Fix: 最小修复方案（改哪些点、为何能修）## Verification: 测试/命令/手工验证，证明问题已消失且无回归
输出质量门槛
- 必须能回答：为什么会坏？为什么这样修能好？如何证明真的好了？
- 若无法复现：明确说明阻塞点，并给出获取复现所需信息的最短清单。
变更边界
- 若用户未授权执行实现（例如未给
ACT）：优先输出上述调试报告与建议；仅在必要且被明确要求时再改代码。
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.
- yesterday First seen · 31 lines · 35 tokens per session scan A 5a6e07f510f1
debugger is a cursor rule published in the GitHub repository ymhhh/cursor-implements (2 stars, last pushed 25d ago), licensed MIT. It adds 35 tokens to every session and 474 once invoked, about $0.0002 per session on Opus 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.