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/ivangrynenko/cursorrulesWrote 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/rules/ivangrynenko/cursorrules/debugging-standards)<a href="https://agentmods.dev/rules/ivangrynenko/cursorrules/debugging-standards"><img src="https://agentmods.dev/badge/rules/ivangrynenko/cursorrules/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.
<a href="https://agentmods.dev/rules/ivangrynenko/cursorrules/debugging-standards"><img src="https://agentmods.dev/badge/rules/ivangrynenko/cursorrules/debugging-standards.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.00239 | $0.00239 |
| Opus 5.5 | $0.00096 | $0.00096 |
| Sonnet 5.5 | $0.00048 | $0.00048 |
| Haiku 4.5 | $0.00024 | $0.00024 |
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.
What it actually says
Debugging Standards
Ensures proper debugging practices and error handling.
Rule Details
-
Name: debugging_standards
-
Description: Enforce standards for debugging and error handling
Filters
- file extension pattern:
\\.(php|js|ts|vue|jsx|tsx|py)$
Enforcement Checks
- Conditions:
- pattern
console\\.log\\(|print_r\\(|var_dump\\(– Replace debug statements with proper logging - pattern
catch\\s*\\([^)]*\\)\\s*\\{\\s*\\}– Implement proper error handling in catch blocks
- pattern
Suggestions
- Guidance: Debugging Best Practices:
- Address root causes, not symptoms
- Add descriptive logging messages
- Create isolated test functions
- Implement comprehensive error handling
- Use appropriate logging levels
- Add context to error messages
- Consider debugging tools integration
Metadata
- Priority: high
- Version: 1.1
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 · 38 lines · 239 tokens per session scan A f99427d76476
debugging-standards is a cursor rule published in the GitHub repository ivangrynenko/cursorrules (88 stars, last pushed 11mo ago), licensed MIT. It adds 239 tokens to every session, about $0.0010 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-30.
Other cursor rules, from other repositories
performance
Performance: profiling-first optimization, caching, bottleneck patterns.
error-handling
Error handling: typed errors, boundaries, user messages.
logging
Logging: structured logs, levels, correlation.
vscode
VS Code: settings, extensions, workspace config.
06-error-handling
Cursor rule "06-error-handling" from orbitalsonic/AndroidPilot, covering error handling, never, always, coroutines and validation.
network-troubleshoot
Systematic, safety-first network troubleshooting for developers.