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/paulpham157/paul-s-cursor-rules/debugging-and-testing-rulesgit clone --depth 1 https://github.com/paulpham157/paul-s-cursor-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/rules/paulpham157/paul-s-cursor-rules/debugging-and-testing-rules)<a href="https://agentmods.dev/rules/paulpham157/paul-s-cursor-rules/debugging-and-testing-rules"><img src="https://agentmods.dev/badge/rules/paulpham157/paul-s-cursor-rules/debugging-and-testing-rules.svg" alt="Measured on agentmods" 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 | $0.00053 | $0.00053 |
| Opus 5 | $0.00026 | $0.00026 |
| Sonnet 5 | $0.00011 | $0.00011 |
| Haiku 4.5 | $0.00005 | $0.00005 |
Grade A, and why
debugging-and-testing-rules 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 3d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- debugging-and-testing-rules — 100% identical, 0 lines differ
- debugging-and-testing-rules — 100% identical, 0 lines differ
What it actually says
description: Specifies practices for debugging and testing, including logging, unit tests, and ensuring all tests pass. globs: **/.
- Include debug information in log files.
- Write unit tests for new code.
- Ensure all tests pass before merging.
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.
- 3d ago First seen · 7 lines · 53 tokens per session scan A 51df1ddb0a4f
debugging-and-testing-rules is a cursor rule published in the GitHub repository paulpham157/paul-s-cursor-rules (27 stars, last pushed 1y ago), licensed MIT. It adds 53 tokens to every session, about $0.0003 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-30.
Other cursor rules, from other repositories
convex-cursorrules-prompt-file
Cursor rules for Convex development with best practices.
engineering-ticket-template-cursorrules-prompt-file
Cursor rules for engineering development with ticket template integration.
code-style-consistency-cursorrules-prompt-file
Cursor rules for code development with style consistency integration.
cypress-defect-tracking-cursorrules-prompt-file
Cursor rules for Cypress development with defect tracking.
cypress-integration-testing-cursorrules-prompt-file
Cursor rules for Cypress development with integration testing.
go-backend-scalability-cursorrules-prompt-file
Cursor rules for Go development with backend scalability.