What is debugging-standards?

Rules for debugging and error handling in software. Debugging is the process of finding and fixing the cause of a problem, while error handling controls what happens when code fails.

Use them when reviewing code for leftover debug statements, empty catch blocks, descriptive logging, appropriate error levels, and isolated tests.

They help remove temporary output, prevent empty error handlers, and encourage logs and error messages that explain what happened.

debugging-standards — Cursor rule for Cursor by abderrahimghazali

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/abderrahimghazali/cursor-rules

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/abderrahimghazali/cursor-rules/debugging-standards/github.svg)](https://agentmods.dev/rules/abderrahimghazali/cursor-rules/debugging-standards)

Your own site

<a href="https://agentmods.dev/rules/abderrahimghazali/cursor-rules/debugging-standards"><img src="https://agentmods.dev/badge/rules/abderrahimghazali/cursor-rules/debugging-standards/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/abderrahimghazali/cursor-rules/debugging-standards"><img src="https://agentmods.dev/badge/rules/abderrahimghazali/cursor-rules/debugging-standards.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 263 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.00000	$0.00263
Opus 5.5	$0.00000	$0.00105
Sonnet 5.5	$0.00000	$0.00053
Haiku 4.5	$0.00000	$0.00026

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

Security

Grade A, and why

debugging-standards 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/debugging-standards.mdc · 39 lines

What it actually says